qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ben Widawsky <ben.widawsky@intel.com>
To: Saransh Gupta1 <saransh@ibm.com>
Cc: qemu-devel@nongnu.org, linux-cxl@vger.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: Follow-up on the CXL discussion at OFTC
Date: Thu, 18 Nov 2021 17:52:07 -0800	[thread overview]
Message-ID: <20211119015207.62fhk5mjmvaj5nz4@intel.com> (raw)
In-Reply-To: <OF164E5BA6.E927FE73-ON00258791.0078E206-88258791.007ABBAD@ibm.com>

On 21-11-18 15:20:34, Saransh Gupta1 wrote:
> Hi Ben and Jonathan,
> 
> Thanks for your replies. I'm looking forward to the patches.
> 
> For QEMU, I see hotplug support as an item on the list and would like to 
> start working on it. It would be great if you can provide some pointers 
> about how I should go about it.

It's been a while, so I can't recall what's actually missing. I think it should
mostly behave like a normal PCIe endpoint.

> Also, which version of kernel and QEMU (maybe Jonathan's upcoming version) 
> would be a good starting point for it?

If he rebased and claims it works I have no reason to doubt it :-). I have a
small fix on my v4 branch if you want to use the latest port patches.

> 
> Thanks,
> Saransh
> 
> 
> 
> From:   "Jonathan Cameron" <Jonathan.Cameron@Huawei.com>
> To:     "Ben Widawsky" <ben.widawsky@intel.com>
> Cc:     "Saransh Gupta1" <saransh@ibm.com>, <linux-cxl@vger.kernel.org>, 
> <qemu-devel@nongnu.org>
> Date:   11/17/2021 09:32 AM
> Subject:        [EXTERNAL] Re: Follow-up on the CXL discussion at OFTC
> 
> 
> 
> On Wed, 17 Nov 2021 08:57:19 -0800
> Ben Widawsky <ben.widawsky@intel.com> wrote:
> 
> > Hi Saransh. Please add the list for these kind of questions. I've 
> converted your
> > HTML mail, but going forward, the list will eat it, so please use text 
> only.
> > 
> > On 21-11-16 00:14:33, Saransh Gupta1 wrote:
> > >    Hi Ben,
> > > 
> > >    This is Saransh from IBM. Sorry to have (unintentionally) dropped 
> out
> > >    of the conversion on OFTC, I'm new to IRC.
> > >    Just wanted to follow-up on the discussion there. We discussed 
> about
> > >    helping with linux patches reviews. On that front, I have 
> identified
> > >    some colleague(s) who can help me with this. Let me know if/how you
> > >    want to proceed with that. 
> > 
> > Currently the ball is in my court to re-roll the RFC v2 patches [1] 
> based on
> > feedback from Dan. I've implemented all/most of it, but I'm still 
> debugging some
> > issues with the result.
> > 
> > > 
> > >    Maybe not urgently, but my team would also like to get an 
> understanding
> > >    of the missing pieces in QEMU. Initially our focus is on type3 
> memory
> > >    access and hotplug support. Most of the work that my team does is
> > >    open-source, so contributing to the QEMU effort is another possible
> > >    line of collaboration. 
> > 
> > If you haven't seen it already, check out my LPC talk [2]. The QEMU 
> patches
> > could use a lot of love. Mostly, I have little/no motivation until 
> upstream
> > shows an interest because I don't have time currently to make sure I 
> don't break
> > vs. upstream. If you want more details here, I can provide them, and I 
> will Cc
> > the qemu-devel mailing list; the end of the LPC talk [2] does have a 
> list.
> Hi Ben, Saransh
> 
> I have a forward port of the series + DOE etc to near current QEMU that is 
> lightly tested,
> and can look to push that out publicly later this week.
> 
> I'd also like to push QEMU support forwards and to start getting this 
> upstream in QEMU
> + fill in some of the missing parts.
> 
> Was aiming to make progress on this a few weeks ago, but as ever other 
> stuff
> got in the way.
> 
> +CC qemu-devel in case anyone else also looking at this.
> 
> Jonathan
> 
> 
> 
> > 
> > > 
> > >    Thanks for your help and guidance!
> > > 
> > >    Best,
> > >    Saransh Gupta
> > >    Research Staff Member, IBM Research 
> > 
> > [1]: 
> https://lore.kernel.org/linux-cxl/20211022183709.1199701-1-ben.widawsky@intel.com/T/#t 
> 
> > [2]: 
> https://www.youtube.com/watch?v=g89SLjt5Bd4&list=PLVsQ_xZBEyN3wA8Ej4BUjudXFbXuxhnfc&index=49 
> 
> 
> 
> 
> 
> 


  parent reply	other threads:[~2021-11-19  1:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF255704A1.78FEF164-ON0025878E.00821084-0025878F.00015560@ibm.com>
     [not found] ` <20211117165719.pqig62t5z2grgjvv@intel.com>
2021-11-17 17:32   ` Follow-up on the CXL discussion at OFTC Jonathan Cameron
2021-11-18 22:20     ` Saransh Gupta1
2021-11-18 22:52       ` Shreyas Shah via
2021-11-19  1:48         ` Ben Widawsky
2021-11-19  2:29           ` Shreyas Shah via
2021-11-19  3:25             ` Ben Widawsky
2021-11-26 12:08               ` Alex Bennée
2021-11-29 17:16                 ` Ben Widawsky
2021-11-29 18:28                   ` Alex Bennée
2021-11-30 13:09                     ` Jonathan Cameron via
2021-11-30 17:21                       ` Ben Widawsky
2021-12-01  9:55                         ` Jonathan Cameron via
2021-12-01 10:29                           ` Alex Bennée
2021-11-19  1:52       ` Ben Widawsky [this message]
2021-11-19 18:53         ` Jonathan Cameron
2021-11-19 20:21           ` Ben Widawsky
2021-11-26 10:59           ` Jonathan Cameron via

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=20211119015207.62fhk5mjmvaj5nz4@intel.com \
    --to=ben.widawsky@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=saransh@ibm.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).