qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Peter Xu <peterx@redhat.com>, Jason Wang <jasowang@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Eduardo Habkost <eduardo@habkost.net>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] intel-iommu: Report interrupt remapping faults, fix return value
Date: Tue, 17 Oct 2023 17:28:26 -0400	[thread overview]
Message-ID: <20231017172812-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <c72aa2174f60f184e87636a0a3a0394ef8e7afd3.camel@infradead.org>

On Tue, Oct 17, 2023 at 10:19:55PM +0100, David Woodhouse wrote:
> On Wed, 2023-08-23 at 11:37 -0400, Peter Xu wrote:
> > On Wed, Aug 23, 2023 at 01:23:25PM +0100, David Woodhouse wrote:
> > > From: David Woodhouse <dwmw@amazon.co.uk>
> > > 
> > > A generic X86IOMMUClass->int_remap function should not return VT-d
> > > specific values; fix it to return 0 if the interrupt was successfully
> > > translated or -EINVAL if not.
> > > 
> > > The VTD_FR_IR_xxx values are supposed to be used to actually raise
> > > faults through the fault reporting mechanism, so do that instead for
> > > the case where the IRQ is actually being injected.
> > > 
> > > There is more work to be done here, as pretranslations for the KVM IRQ
> > > routing table can't fault; an untranslatable IRQ should be handled in
> > > userspace and the fault raised only when the IRQ actually happens (if
> > > indeed the IRTE is still not valid at that time). But we can work on
> > > that later; we can at least raise faults for the direct case.
> > > 
> > > Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> > 
> > Acked-by: Peter Xu <peterx@redhat.com>
> 
> Thanks.
> 
> What do I do with this next? It's still lurking in my working tree.
> 
> 

Not sure how I lost it. Sorry. Will pick up.



  reply	other threads:[~2023-10-17 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 12:23 [PATCH v2] intel-iommu: Report interrupt remapping faults, fix return value David Woodhouse
2023-08-23 15:37 ` Peter Xu
2023-10-17 21:19   ` David Woodhouse
2023-10-17 21:28     ` Michael S. Tsirkin [this message]
2023-10-17 21:29       ` David Woodhouse
2023-10-18 15:46         ` Michael S. Tsirkin
2023-10-19  8:18           ` David Woodhouse

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=20231017172812-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=eduardo@habkost.net \
    --cc=jasowang@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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).