From: "Michael S. Tsirkin" <mst@redhat.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: hans@linux.alibaba.com, herongguang@linux.alibaba.com,
zmlcc@linux.alibaba.com, dust.li@linux.alibaba.com,
tonylu@linux.alibaba.com, zhenzao@linux.alibaba.com,
helinguo@linux.alibaba.com, gerry@linux.alibaba.com,
cohuck@redhat.com, jasowang@redhat.com,
virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] Re: [PATCH] content: reserve device ID 44 for ISM device
Date: Thu, 15 Dec 2022 04:28:42 -0500 [thread overview]
Message-ID: <20221215042820-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221215042635-mutt-send-email-mst@kernel.org>
On Thu, Dec 15, 2022 at 04:28:00AM -0500, Michael S. Tsirkin wrote:
> On Wed, Nov 23, 2022 at 07:21:37PM +0800, Xuan Zhuo wrote:
> > On Wed, 23 Nov 2022 19:21:09 +0800, Xuan Zhuo <xuanzhuo@linux.alibaba.com> wrote:
> > > The virtio-ism device provides the ability to share memory between
> > > different guests on a host. A guest's memory got from ism device can be
> > > shared with multiple peers at the same time. This shared relationship
> > > can be dynamically created and released.
> > >
> > > The shared memory obtained from the device is divided into multiple ism
> > > regions for share. ISM device provides a mechanism to notify other ism
> > > region referrers of content update events.
> >
> > The last spec version:
> >
> > https://lists.oasis-open.org/archives/virtio-dev/202211/msg00001.html
> >
> > Thanks.
>
> Hello!
> Please note specification comments (including proposals) must be
> posted to virtio-comments, virtio-dev is for implementation
> discussions. Please post to the correct list.
>
> Thanks!
To add to that, you can CC virtio-dev if you like, and it's
even encouraged.
>
> >
> > >
> > > This patch is to reserve the next available device ID for virtio-ism.
> > >
> > > Signed-off-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > > ---
> > > content.tex | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/content.tex b/content.tex
> > > index 91ba76c..7302365 100644
> > > --- a/content.tex
> > > +++ b/content.tex
> > > @@ -2992,6 +2992,8 @@ \chapter{Device Types}\label{sec:Device Types}
> > > \hline
> > > 43 & Camera device \\
> > > \hline
> > > +44 & ISM device \\
> > > +\hline
> > > \end{tabular}
> > >
> > > Some of the devices above are unspecified by this document,
> > > --
> > > 2.32.0.3.g01195cf9f
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2022-12-15 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 11:21 [PATCH] content: reserve device ID 44 for ISM device Xuan Zhuo
2022-11-23 11:21 ` Xuan Zhuo
2022-12-15 9:27 ` [virtio-dev] " Michael S. Tsirkin
2022-12-15 9:28 ` Michael S. Tsirkin [this message]
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=20221215042820-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=dust.li@linux.alibaba.com \
--cc=gerry@linux.alibaba.com \
--cc=hans@linux.alibaba.com \
--cc=helinguo@linux.alibaba.com \
--cc=herongguang@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.com \
--cc=zhenzao@linux.alibaba.com \
--cc=zmlcc@linux.alibaba.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