From: Saurabh Singh Sengar Sent: Wednesday,
February 12, 2025 7:07 PM
>
> On Thu, Feb 13, 2025 at 01:35:22AM +, Michael Kelley wrote:
> > From: Saurabh Singh Sengar Sent: Monday,
> > February 10, 2025 8:52 AM
> > >
> > [snip]
> > > > > >
> > > > > > While we are at it, I want to mention th
On Thu, Feb 13, 2025 at 01:35:22AM +, Michael Kelley wrote:
> From: Saurabh Singh Sengar Sent: Monday,
> February 10, 2025 8:52 AM
> >
> [snip]
> > > > >
> > > > > While we are at it, I want to mention that I also observed below WARN
> > > > > while removing the hyperv_fb, but that needs a s
From: Saurabh Singh Sengar Sent: Monday, February
10, 2025 8:52 AM
>
[snip]
> > > >
> > > > While we are at it, I want to mention that I also observed below WARN
> > > > while removing the hyperv_fb, but that needs a separate fix.
> > > >
> > > >
> > > > [ 44.111220] WARNING: CPU: 35 PID: 1882
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
From: Saurabh Singh Sengar Sent: Monday, February
10, 2025 8:52 AM
>
> On Mon, Feb 10, 2025 at 06:58:25AM -0800, Saurabh Singh Sengar wrote:
> > On Mon, Feb 10, 2025 at 02:28:35PM +, Michael Kelley wrote:
> > > From: Saurabh Singh Sengar Sent: Monday,
> > > February 10, 2025 4:41 AM
> > >
On Mon, Feb 10, 2025 at 06:58:25AM -0800, Saurabh Singh Sengar wrote:
> On Mon, Feb 10, 2025 at 02:28:35PM +, Michael Kelley wrote:
> > From: Saurabh Singh Sengar Sent: Monday,
> > February 10, 2025 4:41 AM
> > >
> > > On Sun, Feb 09, 2025 at 03:52:52PM -0800, mhkelle...@gmail.com wrote:
> >
On Mon, Feb 10, 2025 at 02:28:35PM +, Michael Kelley wrote:
> From: Saurabh Singh Sengar Sent: Monday,
> February 10, 2025 4:41 AM
> >
> > On Sun, Feb 09, 2025 at 03:52:52PM -0800, mhkelle...@gmail.com wrote:
> > > From: Michael Kelley
> > >
> > > When a Hyper-V framebuffer device is remove
From: Saurabh Singh Sengar Sent: Monday, February
10, 2025 4:41 AM
>
> 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 mem
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
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 framebuffer must
be unmapped. Current code unmaps the wrong address, resulting i
10 matches
Mail list logo
