Linux CXL
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: Dan J Williams <dan.j.williams@intel.com>,
	Adam Manzanares <a.manzanares@samsung.com>, <vhache@rambus.com>,
	<linux-cxl@vger.kernel.org>
Subject: Re: [RFC] Do we need dedicated LSF/MM/BPF 2024 session for CXL memory?
Date: Mon, 8 Jan 2024 12:41:03 +0000	[thread overview]
Message-ID: <20240108124103.00004afd@Huawei.com> (raw)
In-Reply-To: <42978BEA-D194-41F4-A619-BAF02CE8F4FF@dubeyko.com>

On Fri, 22 Dec 2023 18:10:21 +0300
Viacheslav Dubeyko <slava@dubeyko.com> wrote:


> 
> Hi Jonathan,
> 
> I think QEMU is important area of CXL memory emulation and testing.
> So, I assume we could have interesting topics and discussions here.
> Any suggestions for this? What do you think?

Currently I'm not seeing anything that would really suit LSF-MM.
There's lots going on it just won't much benefit from the people I'd
expect to talk to in that venue (about QEMU emulation side of things
anyway - even the virtualization topics are going to be too early stage
to really discuss much this year).

Also from person point of view, I'm avoiding travel until the summer.
Might participate remotely.

Jonathan

> 
> Thanks,
> Slava.
> 
> 
> 


  parent reply	other threads:[~2024-01-08 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20231222151028uscas1p1fa4d0282844f4aaa36b1133c5df17c9c@uscas1p1.samsung.com>
2023-12-22 15:10 ` [RFC] Do we need dedicated LSF/MM/BPF 2024 session for CXL memory? Viacheslav Dubeyko
2024-01-03 16:53   ` Adam Manzanares
2024-01-15  8:58     ` Viacheslav Dubeyko
2024-01-31 18:25       ` Adam Manzanares
2024-01-08 12:41   ` Jonathan Cameron [this message]
2024-01-16 19:21   ` Dan Williams

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=20240108124103.00004afd@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --cc=vhache@rambus.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