From: Joel Granados <j.granados@samsung.com>
To: Klaus Jensen <its@irrelevant.dk>
Cc: <k.jensen@samsung.com>, <qemu-devel@nongnu.org>, <qemu-block@nongnu.org>
Subject: Re: [PATCH v2 2/3] nvme: Add ocp to the subsys
Date: Wed, 16 Nov 2022 16:02:51 +0100 [thread overview]
Message-ID: <20221116150251.qtrgjbcncbjjjjin@localhost> (raw)
In-Reply-To: <Y3Nz9ieSaj0mHvRy@cormorant.local>
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
On Tue, Nov 15, 2022 at 12:11:50PM +0100, Klaus Jensen wrote:
> On Nov 14 14:50, Joel Granados wrote:
> > The Open Compute Project defines a Datacenter NVMe SSD Spec that sits on
> > top of the NVMe spec. Additional commands and NVMe behaviors specific for
> > the Datacenter. This is a preparation patch that introduces an argument to
> > activate OCP in nvme.
> >
> > Signed-off-by: Joel Granados <j.granados@samsung.com>
> > ---
> > hw/nvme/nvme.h | 1 +
> > hw/nvme/subsys.c | 4 ++--
> > 2 files changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/nvme/nvme.h b/hw/nvme/nvme.h
> > index 79f5c281c2..aa99c0c57c 100644
> > --- a/hw/nvme/nvme.h
> > +++ b/hw/nvme/nvme.h
> > @@ -56,6 +56,7 @@ typedef struct NvmeSubsystem {
> >
> > struct {
> > char *nqn;
> > + bool ocp;
> > } params;
> > } NvmeSubsystem;
> >
> > diff --git a/hw/nvme/subsys.c b/hw/nvme/subsys.c
> > index 9d2643678b..ecca28449c 100644
> > --- a/hw/nvme/subsys.c
> > +++ b/hw/nvme/subsys.c
> > @@ -129,8 +129,8 @@ static void nvme_subsys_realize(DeviceState *dev, Error **errp)
> >
> > static Property nvme_subsystem_props[] = {
> > DEFINE_PROP_STRING("nqn", NvmeSubsystem, params.nqn),
> > - DEFINE_PROP_END_OF_LIST(),
> > -};
> > + DEFINE_PROP_BOOL("ocp", NvmeSubsystem, params.ocp, false),
>
> It is the controller that implements the OCP specification, not the
> namespace or the subsystem. The parameter should be on the controller
> device.
Makes sense. I'll put the option in hw/nvme/ctrl.c
>
> We discussed that the Get Log Page was subsystem scoped and not
> namespace scoped, but that is unrelated to this.
Yep, this was the confusion. Thx for clarifying.
>
> > + DEFINE_PROP_END_OF_LIST(), };
> >
> > static void nvme_subsys_class_init(ObjectClass *oc, void *data)
> > {
> > --
> > 2.30.2
> >
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-11-16 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221114135426eucas1p271a54e44af5a53a45a7393ed34585ee0@eucas1p2.samsung.com>
2022-11-14 13:50 ` [PATCH v2 0/3] Add OCP extended log to nvme QEMU Joel Granados
2022-11-14 13:50 ` [PATCH v2 1/3] nvme: Move adjustment of data_units{read,written} Joel Granados
2022-11-15 11:09 ` Klaus Jensen
2022-11-14 13:50 ` [PATCH v2 2/3] nvme: Add ocp to the subsys Joel Granados
2022-11-15 11:11 ` Klaus Jensen
2022-11-16 15:02 ` Joel Granados [this message]
2022-11-14 13:50 ` [PATCH v2 3/3] nvme: Add physical writes/reads from OCP log Joel Granados
2022-11-15 11:26 ` Klaus Jensen
2022-11-16 16:19 ` Joel Granados
2022-11-17 6:36 ` Klaus Jensen
2022-12-23 7:39 ` [PATCH v2 0/3] Add OCP extended log to nvme QEMU Christoph Hellwig
2023-01-04 14:43 ` Joel Granados
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=20221116150251.qtrgjbcncbjjjjin@localhost \
--to=j.granados@samsung.com \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.