iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 4 Feb 2021 13:25:24 -0700	[thread overview]
Message-ID: <20210204202524.GO702808@redhat.com> (raw)
In-Reply-To: <YBpjAF3Q+NeJblE9@myrica>

On 03 Feb 2021 09:46, Jean-Philippe Brucker wrote:
> On Tue, Feb 02, 2021 at 01:27:13PM -0700, Al Stone wrote:
> > On 02 Feb 2021 10:17, Jean-Philippe Brucker wrote:
> > > Hi Al,
> > > 
> > > On Fri, Dec 04, 2020 at 01:18:25PM -0700, Al Stone wrote:
> > > > > 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.
> > > 
> > > Has there been any more feedback on the VIOT specification? I'm wondering
> > > when we can start upstreaming support for it.
> > > 
> > > Thanks,
> > > Jean
> > 
> > Ah, sorry, Jean.  I meant to get back to you sooner.  My apologies.
> > 
> > The latest version that resulted from the discussion with Yinghan of
> > Microsoft is the one in front the ASWG; I think if you upstream that
> > version, it should be identical to the spec when it is next published
> > (post ACPI 6.4).
> > 
> > The process is: (1) propose the change, (2) review it in committee,
> > (3) give people more time to think about it, then (4) have a finale
> > vote.  We've been iterating over (1), (2) and (3).  Since there was
> > no new discussion at the last meeting, we should have the final vote
> > on this (4) in the next meeting.  I had hoped we could do that last
> > week but the meeting was canceled at the last minute.  I hope to have
> > the final vote this Thursday and will let you know as soon as it has
> > been decided.
> > 
> > My apologies for the delays; getting things done by committee always
> > takes a bazillion times longer than one would think.
> 
> No worries, thanks a lot for the update!
> 
> Thanks,
> Jean

Sigh.  Just got a note that today's meeting has been canceled :(.

So, next week for the final vote.  OTOH, there have been no comments
of any sort on the proposal -- and silence is good, in this case.

-- 
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

  reply	other threads:[~2021-02-04 20:25 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
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 [this message]
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=20210204202524.GO702808@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 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).