On Tue, Oct 08, 2024 at 04:59:45PM +0800, Chenyi Qiang wrote:
> Hi Paolo,
>
> Kindly ping for this thread. The in-place page conversion is discussed
> at Linux Plumbers. Does it give some direction for shared device
> assignment enabling work?
>
Hi everybody.
Our NVIDIA GPUs currently support thi
On 15.11.24 17:47, Rob Nertney wrote:
On Tue, Oct 08, 2024 at 04:59:45PM +0800, Chenyi Qiang wrote:
Hi Paolo,
Kindly ping for this thread. The in-place page conversion is discussed
at Linux Plumbers. Does it give some direction for shared device
assignment enabling work?
Hi everybody.
Hi,
Hi Paolo,
Kindly ping for this thread. The in-place page conversion is discussed
at Linux Plumbers. Does it give some direction for shared device
assignment enabling work?
Thanks
Chenyi
On 8/16/2024 11:02 AM, Chenyi Qiang wrote:
> Hi Paolo,
>
> Hope to draw your attention. As TEE I/O would depe
Hi Paolo,
Hope to draw your attention. As TEE I/O would depend on shared device
assignment and we introduce this RDM solution in QEMU. Now, Observe the
in-place private/shared conversion option mentioned by David, do you
think we should continue to add pass-thru support for this in-qemu page
conve
On 7/31/2024 7:18 PM, David Hildenbrand wrote:
> Sorry for the late reply!
>
>>> Current users must skip it, yes. How private memory would have to be
>>> handled, and who would handle it, is rather unclear.
>>>
>>> Again, maybe we'd want separate RamDiscardManager for private and shared
>>> mem
Hi David,
On 7/26/2024 3:20 PM, David Hildenbrand wrote:
Yes, there have been discussions about that, also in the context of
supporting huge pages while allowing for the guest to still convert
individual 4K chunks ...
A summary is here [1]. Likely more things will be covered at Linux
Plumber
Sorry for the late reply!
Current users must skip it, yes. How private memory would have to be
handled, and who would handle it, is rather unclear.
Again, maybe we'd want separate RamDiscardManager for private and shared
memory (after all, these are two separate memory backends).
We also cons
On 31.07.24 09:12, Xu Yilun wrote:
On Fri, Jul 26, 2024 at 09:08:51AM +0200, David Hildenbrand wrote:
On 26.07.24 07:02, Tian, Kevin wrote:
From: David Hildenbrand
Sent: Thursday, July 25, 2024 10:04 PM
Open
Implementing a RamDiscardManager to notify VFIO of page conversions
causes chan
On Fri, Jul 26, 2024 at 09:08:51AM +0200, David Hildenbrand wrote:
> On 26.07.24 07:02, Tian, Kevin wrote:
> > > From: David Hildenbrand
> > > Sent: Thursday, July 25, 2024 10:04 PM
> > >
> > > > Open
> > > >
> > > > Implementing a RamDiscardManager to notify VFIO of page conversions
> > > >
On 7/26/2024 3:20 PM, David Hildenbrand wrote:
> On 26.07.24 08:20, Chenyi Qiang wrote:
>>
>>
>> On 7/25/2024 10:04 PM, David Hildenbrand wrote:
Open
Implementing a RamDiscardManager to notify VFIO of page conversions
causes changes in semantics: private memory is treate
On 26.07.24 08:20, Chenyi Qiang wrote:
On 7/25/2024 10:04 PM, David Hildenbrand wrote:
Open
Implementing a RamDiscardManager to notify VFIO of page conversions
causes changes in semantics: private memory is treated as discarded (or
hot-removed) memory. This isn't aligned with the expectat
On 26.07.24 07:02, Tian, Kevin wrote:
From: David Hildenbrand
Sent: Thursday, July 25, 2024 10:04 PM
Open
Implementing a RamDiscardManager to notify VFIO of page conversions
causes changes in semantics: private memory is treated as discarded (or
hot-removed) memory. This isn't aligned wit
On 7/25/2024 10:04 PM, David Hildenbrand wrote:
>> Open
>>
>> Implementing a RamDiscardManager to notify VFIO of page conversions
>> causes changes in semantics: private memory is treated as discarded (or
>> hot-removed) memory. This isn't aligned with the expectation of current
>> RamDisca
> From: David Hildenbrand
> Sent: Thursday, July 25, 2024 10:04 PM
>
> > Open
> >
> > Implementing a RamDiscardManager to notify VFIO of page conversions
> > causes changes in semantics: private memory is treated as discarded (or
> > hot-removed) memory. This isn't aligned with the expectati
Open
Implementing a RamDiscardManager to notify VFIO of page conversions
causes changes in semantics: private memory is treated as discarded (or
hot-removed) memory. This isn't aligned with the expectation of current
RamDiscardManager users (e.g. VFIO or live migration) who really
expect that
Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
discard") effectively disables device assignment with guest_memfd.
guest_memfd is required for confidential guests, so device assignment to
confidential guests is disabled. A supporting assumption for disabling
device-assignment w
16 matches
Mail list logo
