On Sat, Mar 01, 2025 at 08:16:29AM -0800, Saurabh Sengar wrote:
> This patch series addresses an issue in the unbind path of the hyperv_fb
> driver, which is resolved in the second patch of this series.
>
> While working on this fix, it was observed that hvfb_putmem() and its
> child functions cou
On Tue, Feb 18, 2025 at 03:01:30PM -0800, mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer
> device. When the kdump kernel runs in such a VM, loading the efifb
> driver may hang because of accessing the framebuffer at the wr
the
> > > > solution that isn't related to the code changes in c25a19afb81c.
> > > >
> > > >drivers/video/fbdev/hyperv_fb.c | 20 +---
> > > >1 file changed, 13 insertions(+), 7 deletions(-)
> > >
> > > a
On Mon, Feb 10, 2025 at 11:34:41AM -0800, mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> When a Hyper-V DRM device is probed, the driver allocates MMIO space for
> the vram, and maps it cacheable. If the device removed, or in the error
> path for device probing, the MMIO space is released
On Sun, Feb 09, 2025 at 03:52:52PM -0800, mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> When a Hyper-V framebuffer device is removed, or the driver is unbound
> from a device, any allocated and/or mapped memory must be released. In
> particular, MMIO address space that was mapped to the
ame = "hyperv_record_panic_msg",
> .data = &sysctl_record_panic_msg,
Acked-by: Wei Liu
On Thu, Sep 05, 2024 at 10:30:56AM +0200, Helge Deller wrote:
> On 9/5/24 09:25, Wei Liu wrote:
> > On Mon, Sep 02, 2024 at 03:44:02PM +0800, Chen Ni wrote:
> > > Replace a comma between expression statements by a semicolon.
> > >
> > > Fixes: d786e00d19f9 (&
On Mon, Sep 02, 2024 at 03:44:02PM +0800, Chen Ni wrote:
> Replace a comma between expression statements by a semicolon.
>
> Fixes: d786e00d19f9 ("drivers: hv, hyperv_fb: Untangle and refactor Hyper-V
> panic notifiers")
> Signed-off-by: Chen Ni
Applied to hyperv-fixes, thanks!
> ---
> driver
On Fri, Feb 09, 2024 at 04:53:37PM +0100, Helge Deller wrote:
> On 2/9/24 16:23, Michael Kelley wrote:
> > From: Thomas Zimmermann Sent: Thursday, February 1,
> > 2024 12:17 AM
[...]
> >
> > Wei Liu and Helge Deller --
> >
> > Should this fix go thr
On Wed, Nov 01, 2023 at 09:01:48AM -0700, Nischala Yelchuri wrote:
> Current Hyper-V code for CoCo VMs uses ioremap_cache() to map normal memory
> as decrypted.
> ioremap_cache() is ideally used to map I/O device memory when it has the
> characteristics
> of normal memory. It should not be used t
Please change the prefix to "Drivers: hv:" in the subject line in the
two patches.
On Thu, Sep 28, 2023 at 03:21:39PM +0200, Joel Granados via B4 Relay wrote:
> From: Joel Granados
>
> This commit comes at the tail end of a greater effort to remove the
> empty elements at the end of the ctl_tabl
On Sun, Sep 11, 2022 at 09:11:42AM -0700, Saurabh Singh Sengar wrote:
> On Sat, Sep 10, 2022 at 08:06:05PM +0200, Thomas Zimmermann wrote:
> > Hi
> >
> > Am 09.09.22 um 17:09 schrieb Saurabh Sengar:
> > >Due to a full ring buffer, the driver may be unable to send updates to
> > >the Hyper-V host.
On Mon, Sep 12, 2022 at 08:32:46AM -0700, Saurabh Sengar wrote:
> Existing code is causing a race condition where dirt_needed value is
> already set by the host and gets overwritten with default value. Remove
> this default setting of dirt_needed, to avoid overwriting the value
> received in the ch
On Sat, Aug 27, 2022 at 03:03:42PM +0200, Vitaly Kuznetsov wrote:
[...]
> Changes since v2re (PATCH3).
>
> Vitaly Kuznetsov (3):
> PCI: Move PCI_VENDOR_ID_MICROSOFT/PCI_DEVICE_ID_HYPERV_VIDEO
> definitions to pci_ids.h
> Drivers: hv: Always reserve framebuffer region for Gen1 VMs
> Drive
On Tue, Aug 30, 2022 at 09:31:54AM +0200, Vitaly Kuznetsov wrote:
> Bjorn Helgaas writes:
>
> > On Sat, Aug 27, 2022 at 03:03:43PM +0200, Vitaly Kuznetsov wrote:
> >> There are already three places in kernel which define
> >> PCI_VENDOR_ID_MICROSOFT
> >> and two for PCI_DEVICE_ID_HYPERV_VIDEO an
On Fri, Aug 05, 2022 at 06:35:01PM +, Michael Kelley (LINUX) wrote:
> From: Christophe JAILLET Sent: Sunday, July
> 31, 2022 1:02 PM
> >
> > hyperv_setup_vram() calls vmbus_allocate_mmio().
> > This must be undone in the error handling path of the probe, as already
> > done in the remove fun
On Sat, May 21, 2022 at 07:23:39AM -0700, Saurabh Sengar wrote:
> There were two different approaches getting used in this driver to
> allocate vram:
> 1. VRAM allocation from PCI region for Gen1
> 2. VRAM alloaction from MMIO region for Gen2
> First approach limilts the vram to PCI BAR
On Fri, May 20, 2022 at 12:20:40AM -0700, Saurabh Sengar wrote:
> There were two different approaches getting used in this driver to
> allocate vram:
> 1. VRAM allocation from PCI region for Gen1
> 2. VRAM alloaction from MMIO region for Gen2
> First approach limilts the vram to PCI BAR
On Mon, May 02, 2022 at 09:36:27AM -0700, Michael Kelley wrote:
> Linux code for running as a Hyper-V guest includes special cases for the
> first released versions of Hyper-V: 2008 and 2008R2/Windows 7. These
> versions were very thinly used for running Linux guests when first
> released more than
On Sun, May 08, 2022 at 03:43:26PM +, Michael Kelley (LINUX) wrote:
> From: Pavel Machek Sent: Wednesday, May 4, 2022 10:23 AM
> >
> > Hi!
> >
> > > Linux code for running as a Hyper-V guest includes special cases for the
> > > first released versions of Hyper-V: 2008 and 2008R2/Windows 7. T
On Tue, May 03, 2022 at 07:50:16AM -0700, Saurabh Singh Sengar wrote:
> On Tue, Apr 12, 2022 at 05:06:07AM +, Dexuan Cui wrote:
> > > From: Saurabh Sengar
> > > Sent: Monday, April 11, 2022 9:29 PM
> > > ...
> > > Add error message when the size of requested framebuffer is more than
> > > the
On Mon, May 02, 2022 at 09:36:27AM -0700, Michael Kelley wrote:
> Linux code for running as a Hyper-V guest includes special cases for the
> first released versions of Hyper-V: 2008 and 2008R2/Windows 7. These
> versions were very thinly used for running Linux guests when first
> released more than
On Wed, Apr 27, 2022 at 06:47:53AM -0700, Saurabh Sengar wrote:
> This patch fixes a bug where GEN1 VMs doesn't allow resolutions greater
> than 64 MB size (eg 7680x4320). Unnecessary PCI check limits Gen1 VRAM
> to legacy PCI BAR size only (ie 64MB). Thus any, resolution requesting
> greater then
On Wed, Apr 06, 2022 at 11:27:07PM -0700, Saurabh Sengar wrote:
> Added error message when the size of requested framebuffer is more then
> the allocated size by vmbus mmio region for framebuffer
>
> Signed-off-by: Saurabh Sengar
> ---
> v1 -> v2 : Corrected Sign-off
>
> drivers/gpu/drm/hyperv/
On Mon, Jan 24, 2022 at 02:48:57PM +0100, Helge Deller wrote:
> On 1/24/22 14:31, Wei Liu wrote:
[...]
> >>
> >> Linus hasn't pulled my tree yet, and he will probably not before the
> >> next merge window. So, if this is an urgent bugfix for you, I can offer
>
On Mon, Jan 24, 2022 at 10:52:22AM +0100, Helge Deller wrote:
> On 1/23/22 23:30, Wei Liu wrote:
> > On Sun, Jan 23, 2022 at 10:27:56PM +, Michael Kelley (LINUX) wrote:
> >> From: Wei Liu Sent: Sunday, January 23, 2022 1:56 PM
> >>>
> >>> On Sun,
On Sun, Jan 23, 2022 at 10:27:56PM +, Michael Kelley (LINUX) wrote:
> From: Wei Liu Sent: Sunday, January 23, 2022 1:56 PM
> >
> > On Sun, Jan 16, 2022 at 09:53:06PM +, Haiyang Zhang wrote:
> > >
> > >
> > > > -Original Message-
>
On Sun, Jan 16, 2022 at 09:53:06PM +, Haiyang Zhang wrote:
>
>
> > -Original Message-
> > From: Michael Kelley (LINUX)
> > Sent: Sunday, January 16, 2022 2:19 PM
> > To: KY Srinivasan ; Haiyang Zhang
> > ; Stephen
> > Hemminger ; wei@kernel.org; Wei Hu
> > ; Dexuan
> > Cui ; dr
On Mon, Jan 10, 2022 at 01:44:19AM +0100, Andrea Parri wrote:
> (Extending Cc: list,)
>
> On Sun, Jan 09, 2022 at 05:55:16PM +0800, Yanming Liu wrote:
> > Commit adae1e931acd ("Drivers: hv: vmbus: Copy packets sent by Hyper-V
> > out of the ring buffer") introduced a notion of maximum packet size
On Fri, Jun 04, 2021 at 02:25:01PM +0200, Vitaly Kuznetsov wrote:
> Hi,
>
> Commit ccf953d8f3d6 ("fb_defio: Remove custom address_space_operations")
> seems to be breaking Hyper-V framebuffer
> (drivers/video/fbdev/hyperv_fb.c) driver for me: Hyper-V guest boots
> well and plymouth even works but
On Mon, May 17, 2021 at 04:59:22AM -0700, Deepak Rawat wrote:
> Maintainer for hyperv synthetic video device.
>
> Signed-off-by: Deepak Rawat
> ---
> MAINTAINERS | 16
> 1 file changed, 16 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index bd7aff0c120f..2613425514
On Tue, Apr 20, 2021 at 08:44:19AM -0700, Michael Kelley wrote:
> Due to a full ring buffer, the driver may be unable to send updates to
> the Hyper-V host. But outputing the error message can make the problem
> worse because console output is also typically written to the frame
> buffer. As a re
freeing the memory and
> leaving the pointer non-NULL, resulting in a double free if an error
> occurs or later if hvfb_remove() is called.
>
> Fix this by removing all kfree(info->apertures) calls in hvfb_getmem().
> This will allow framebuffer_release() to free the memor
Thanks for your patch.
I would like to change the prefix to "video: hyperv_fb:" to be more
specific.
On Tue, Mar 23, 2021 at 12:33:50AM -0700, Lv Yunlong wrote:
> In function hvfb_probe in hyperv_fb.c, it calls hvfb_getmem(hdev, info)
> and return err when info->apertures is freed.
>
> In the er
On Tue, Nov 24, 2020 at 08:33:32AM +, Dexuan Cui wrote:
> Hi Wei Liu,
> Please do not pick up this patch, because actually MMIO VRAM can not work
> with fb_deferred_io.
>
No problem. Thanks for the heads-up.
Wei.
___
dri-devel mail
On Wed, Nov 18, 2020 at 12:20:11AM +, Michael Kelley wrote:
> From: Dexuan Cui Sent: Tuesday, November 17, 2020 4:03
> PM
> >
> > x86 Hyper-V used to essentially always overwrite the effective cache type
> > of guest memory accesses to WB. This was problematic in cases where there
> > is a p
*hvp = __vmalloc(PAGE_SIZE, GFP_KERNEL | __GFP_ZERO);
> }
Acked-by: Wei Liu
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On Wed, Apr 08, 2020 at 01:58:59PM +0200, Christoph Hellwig wrote:
> Use the designated helper for allocating executable kernel memory, and
> remove the now unused PAGE_KERNEL_RX define.
>
> Signed-off-by: Christoph Hellwig
Acked-by: Wei Liu
___
oe Perches
Reviewed-by: Wei Liu
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
rote:
> >>>> On 24/04/18 07:43, Oleksandr Andrushchenko wrote:
> >>>>> On 04/24/2018 01:41 AM, Boris Ostrovsky wrote:
> >>>>>> On 04/23/2018 08:10 AM, Oleksandr Andrushchenko wrote:
> >>>>>>> On 04/23/2018 02:52 PM,
On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote:
> > > the gntdev.
> > >
> > > I think this is generic enough that it could be implemented by a
> > > device not tied to Xen. AFAICT the hyper_dma guys also wanted
> > > something similar to this.
> > You can't just wrap r
41 matches
Mail list logo
