From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: <vishal.l.verma@intel.com>, <fan.ni@samsung.com>,
<a.manzanares@samsung.com>, <mounika.k@samsung.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 1/2] hw/cxl: Add Transfer FW support
Date: Fri, 26 Jan 2024 17:48:26 +0000 [thread overview]
Message-ID: <20240126174826.00006239@Huawei.com> (raw)
In-Reply-To: <vsm7fpp3fbywuzzepbhezzuhewrk5fc3avtvbcrb2nubs3lm2m@y257ghfqmqmr>
On Fri, 26 Jan 2024 09:17:13 -0800
Davidlohr Bueso <dave@stgolabs.net> wrote:
> On Fri, 26 Jan 2024, Jonathan Cameron wrote:
>
> >On Mon, 8 Jan 2024 23:04:35 -0800
> >Davidlohr Bueso <dave@stgolabs.net> wrote:
> >
> >> Per the latest 3.1 spec for supporting firmware update metadata
> >> (no actual buffers). Aborting a xfer is currently unsupported
> >> through a nop.
> >>
> >> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> >Hi Davidlohr.
> >
> >Whilst we may never notice from the OS as we expect it to send valid
> >sets of transfers only, I'd like the emulation to incorporate more
> >of the validity checks the spec requires such as:
> >- Multiple part transfers must all be for same slot - any interleaved
> > ones for other slots result in error.
> >- Retry of previous transfer or one that starts where previous transfer
> > ended - otherwise Out of Order detected.
> >
> >So we have to hold state, and as such will have the information to
> >set the slot as occupied with just one extra flag stored to say it is
> >a FULL or END message.
> >
> >Otherwise lgtm.
>
> I will send a v2 with your feedback. Do you prefer just using your
> latest '2024-26-01-draft' branch?
Yes, that makes my life easiest (though I'm also find dealing with
rebases if you use something reasonable that isn't that)
Nestle it in as far down as possible but after the DCD changes.
Either before or after your scan media set (up to you - they'll
probably get grouped together anyway for sending to Michael).
Thanks!
Jonathan
>
> Thanks,
> Davidlohr
next prev parent reply other threads:[~2024-01-26 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 7:04 [PATCH -qemu 0/2] hw/cxl: Firmware Update support Davidlohr Bueso
2024-01-09 7:04 ` [PATCH 1/2] hw/cxl: Add Transfer FW support Davidlohr Bueso
2024-01-09 22:36 ` fan
2024-01-10 16:43 ` Davidlohr Bueso
2024-01-26 15:42 ` Jonathan Cameron
2024-01-26 17:17 ` Davidlohr Bueso
2024-01-26 17:48 ` Jonathan Cameron [this message]
2024-01-09 7:04 ` [PATCH 2/2] hw/cxl: Add Activate " Davidlohr Bueso
2024-01-26 15:54 ` Jonathan Cameron
2024-01-26 16:57 ` Davidlohr Bueso
2024-01-26 17:35 ` Jonathan Cameron
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=20240126174826.00006239@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mounika.k@samsung.com \
--cc=vishal.l.verma@intel.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