From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Hannes Reinecke <hare@suse.de>
Cc: "David Hildenbrand" <david@redhat.com>,
linux-mm@kvack.org, linux-cxl@vger.kernel.org,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Ira Weiny" <ira.weiny@intel.com>,
"John Groves" <John@Groves.net>,
virtualization@lists.linux.dev,
"Oscar Salvador" <osalvador@suse.de>,
qemu-devel@nongnu.org, "Dave Jiang" <dave.jiang@intel.com>,
"Dan Williams" <dan.j.williams@intel.com>,
linuxarm@huawei.com, wangkefeng.wang@huawei.com,
"John Groves" <jgroves@micron.com>, "Fan Ni" <fan.ni@samsung.com>,
"Navneet Singh" <navneet.singh@intel.com>,
" “Michael S. Tsirkin”" <mst@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [RFC] Virtualizing tagged disaggregated memory capacity (app specific, multi host shared)
Date: Fri, 16 Aug 2024 10:41:10 +0100 [thread overview]
Message-ID: <20240816104110.000012e6@Huawei.com> (raw)
In-Reply-To: <904a433c-0471-4f11-a34b-cef8adf1663c@suse.de>
On Fri, 16 Aug 2024 09:05:46 +0200
Hannes Reinecke <hare@suse.de> wrote:
> On 8/15/24 18:22, Jonathan Cameron wrote:
> > Introduction
> > ============
> >
> > If we think application specific memory (including inter-host shared memory) is
> > a thing, it will also be a thing people want to use with virtual machines,
> > potentially nested. So how do we present it at the Host to VM boundary?
> >
> > This RFC is perhaps premature given we haven't yet merged upstream support for
> > the bare metal case. However I'd like to get the discussion going given we've
> > touched briefly on this in a number of CXL sync calls and it is clear no one is
> > entirely sure what direction make sense. We may briefly touch on this in the
> > LPC CXL uconf, but time will be very limited.
> >
> Thanks for the detailed write-up.
>
> Can't we have an ad-hoc meeting at OSS/LPC to gather interested/relevant
> people to explore ideas around this?
Absolutely. If people want to email me directly (or mention in the thread)
I'll gather up a list of people to try and find a suitable time / place
(and then post that here).
>
> In particular I'd be interested on how to _get_ the application specific
> memory to the application in question. It's easy if you have your own
> application and design it to work on DAX devices. Obviously this
> approach won't work for unmodified applications; however, they really
> might want to use this, too.
That's a good parallel question (as not virtualization specific).
I'd be tempted to enable this path first for aware applications, but longer
term the ability to use this via common allocator libraries (LD_PRELOAD etc)
might make sense (or some other path?)
>
> And, of course, the other mentioned problems are worth discussing, and I
> do agree that the uconf will probably not providing sufficient time for
> this.
>
> Cheers,
>
> Hannes
next prev parent reply other threads:[~2024-08-16 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 16:22 [RFC] Virtualizing tagged disaggregated memory capacity (app specific, multi host shared) Jonathan Cameron via
2024-08-16 7:05 ` Hannes Reinecke
2024-08-16 9:41 ` Jonathan Cameron via [this message]
2024-08-19 2:12 ` John Groves
2024-08-19 15:40 ` Jonathan Cameron via
2024-09-17 19:37 ` Jonathan Cameron via
2024-10-22 14:11 ` Gregory Price
2024-09-17 19:56 ` Jonathan Cameron via
2024-09-18 12:12 ` Jonathan Cameron
2024-09-19 9:09 ` David Hildenbrand
2024-09-20 9:06 ` Gregory Price
2024-10-22 9:33 ` David Hildenbrand
2024-10-22 14:24 ` Gregory Price
2024-10-22 14:35 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240816104110.000012e6@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=John@Groves.net \
--cc=Jonathan.Cameron@Huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=fan.ni@samsung.com \
--cc=hare@suse.de \
--cc=imammedo@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jgroves@micron.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=navneet.singh@intel.com \
--cc=osalvador@suse.de \
--cc=philmd@linaro.org \
--cc=virtualization@lists.linux.dev \
--cc=wangkefeng.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).