From: Al Stone <ahs3@redhat.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: "kevin.tian@intel.com" <kevin.tian@intel.com>,
"mst@redhat.com" <mst@redhat.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Boeuf, Sebastien" <sebastien.boeuf@intel.com>,
Alexander Grest <Alexander.Grest@microsoft.com>,
Yinghan Yang <Yinghan.Yang@microsoft.com>
Subject: Re: [EXTERNAL] Re: Question regarding VIOT proposal
Date: Fri, 4 Dec 2020 13:18:25 -0700 [thread overview]
Message-ID: <20201204201825.GG4343@redhat.com> (raw)
In-Reply-To: <20201204180924.GA1922896@myrica>
On 04 Dec 2020 19:09, Jean-Philippe Brucker wrote:
> Hi,
>
> On Thu, Dec 03, 2020 at 04:01:27PM -0700, Al Stone wrote:
> > On 03 Dec 2020 22:21, Yinghan Yang wrote:
> > > Hi Jean,
> > >
> > > I'm sorry for the delayed response. I think the new "PCI range node" description makes sense. Could you please make this change in the proposal?
> > >
> > > Other than that, the proposal looks good to go.
>
> Thanks for the feedback, I made the change
>
> > >
> > > Thanks,
> > > Yinghan
> >
> > Jean, were you going to update your existing doc first? If you
> > do that, then I can cut and paste the changes into the existing
> > ASWG proposal. Or do you need to send out an RFC to the mailing
> > list first and finalize it there?
>
> I updated the doc: https://jpbrucker.net/virtio-iommu/viot/viot-v9.pdf
> You can incorporate it into the ASWG proposal.
> Changes since v8:
> * One typo (s/programing/programming/)
> * Modified the PCI Range node to include a segment range.
>
> I also updated the Linux and QEMU implementations on branch
> virtio-iommu/devel in https://jpbrucker.net/git/linux/ and
> https://jpbrucker.net/git/qemu/
>
> Thanks again for helping with this
>
> Jean
Perfect. Thanks. I'll update the ASWG info right away.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-12-04 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 0:13 Question regarding VIOT proposal Yinghan Yang via iommu
2020-11-05 13:45 ` Jean-Philippe Brucker
2020-11-05 22:05 ` [EXTERNAL] " Yinghan Yang via iommu
2020-11-06 13:57 ` Jean-Philippe Brucker
2020-12-03 22:21 ` Yinghan Yang via iommu
2020-12-03 23:01 ` Al Stone
2020-12-04 18:09 ` Jean-Philippe Brucker
2020-12-04 18:15 ` Yinghan Yang via iommu
2020-12-04 20:18 ` Al Stone [this message]
2021-02-02 9:17 ` Jean-Philippe Brucker
2021-02-02 20:27 ` Al Stone
2021-02-03 8:46 ` Jean-Philippe Brucker
2021-02-04 20:25 ` Al Stone
2021-02-16 21:31 ` Al Stone
2021-02-17 9:37 ` Jean-Philippe Brucker
2021-02-18 23:39 ` Al Stone
2021-02-19 11:24 ` Jean-Philippe Brucker
2021-02-19 17:35 ` Al Stone
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=20201204201825.GG4343@redhat.com \
--to=ahs3@redhat.com \
--cc=Alexander.Grest@microsoft.com \
--cc=Yinghan.Yang@microsoft.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=sebastien.boeuf@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 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.