qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>, Peter Xu <peterx@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 2/2] intel_iommu: Only allow interrupt remapping to be enabled if it's supported
Date: Thu, 2 Dec 2021 11:53:25 +0800	[thread overview]
Message-ID: <CACGkMEvtrVX8uWciiVfYpBNsaAwRAfP_P4Ja3T4Axvn47WdzNw@mail.gmail.com> (raw)
In-Reply-To: <20211201205113.57299-2-dwmw2@infradead.org>

On Thu, Dec 2, 2021 at 4:58 AM David Woodhouse <dwmw2@infradead.org> wrote:
>
> From: David Woodhouse <dwmw@amazon.co.uk>
>
> We should probably check if we were meant to be exposing IR, before
> letting the guest turn the IRE bit on.

This looks correct, but it's a change of guest noticeable behaviour.
It's probably fine since we don't expect a guest that enable IR
without checking ecap.

So

Acked-by: Jason Wang <jasowang@redhat.com>

>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> ---
>  hw/i386/intel_iommu.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> index ffc852d110..297e1972f8 100644
> --- a/hw/i386/intel_iommu.c
> +++ b/hw/i386/intel_iommu.c
> @@ -2197,6 +2197,7 @@ static void vtd_handle_gcmd_ire(IntelIOMMUState *s, bool en)
>  /* Handle write to Global Command Register */
>  static void vtd_handle_gcmd_write(IntelIOMMUState *s)
>  {
> +    X86IOMMUState *x86_iommu = X86_IOMMU_DEVICE(s);
>      uint32_t status = vtd_get_long_raw(s, DMAR_GSTS_REG);
>      uint32_t val = vtd_get_long_raw(s, DMAR_GCMD_REG);
>      uint32_t changed = status ^ val;
> @@ -2218,7 +2219,8 @@ static void vtd_handle_gcmd_write(IntelIOMMUState *s)
>          /* Set/update the interrupt remapping root-table pointer */
>          vtd_handle_gcmd_sirtp(s);
>      }
> -    if (changed & VTD_GCMD_IRE) {
> +    if ((changed & VTD_GCMD_IRE) &&
> +        x86_iommu_ir_supported(x86_iommu)) {
>          /* Interrupt remap enable/disable */
>          vtd_handle_gcmd_ire(s, val & VTD_GCMD_IRE);
>      }
> --
> 2.31.1
>
>



  reply	other threads:[~2021-12-02  3:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 20:51 [PATCH 1/2] intel_iommu: Support IR-only mode without DMA translation David Woodhouse
2021-12-01 20:51 ` [PATCH 2/2] intel_iommu: Only allow interrupt remapping to be enabled if it's supported David Woodhouse
2021-12-02  3:53   ` Jason Wang [this message]
2021-12-03  7:42     ` Peter Xu
2021-12-02  3:49 ` [PATCH 1/2] intel_iommu: Support IR-only mode without DMA translation Jason Wang
2021-12-03  7:38   ` Peter Xu
2021-12-03 10:46     ` David Woodhouse
2021-12-03 12:14       ` Peter Xu
2021-12-06  6:49         ` Jason Wang
  -- strict thread matches above, loose matches on Subject: below --
2020-10-15 18:34 David Woodhouse
2020-10-15 18:34 ` [PATCH 2/2] intel_iommu: Only allow interrupt remapping to be enabled if it's supported 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=CACGkMEvtrVX8uWciiVfYpBNsaAwRAfP_P4Ja3T4Axvn47WdzNw@mail.gmail.com \
    --to=jasowang@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=ehabkost@redhat.com \
    --cc=mst@redhat.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).