From: Joerg Roedel <joro@8bytes.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: iommu <iommu@lists.linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jiang Liu <jiang.liu@linux.intel.com>
Subject: Re: [PATCH] iommu/vt-d: Don't store SIRTP request
Date: Tue, 19 Aug 2014 13:09:37 +0200 [thread overview]
Message-ID: <20140819110937.GA26492@8bytes.org> (raw)
In-Reply-To: <53E8A555.5010905@siemens.com>
On Mon, Aug 11, 2014 at 01:13:25PM +0200, Jan Kiszka wrote:
> Don't store the SIRTP request bit in the register state. It will
> otherwise become sticky and could request an Interrupt Remap Table
> Pointer update on each command register write.
>
> Found while starting to emulate IR in QEMU, not by observing problems on
> real hardware.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> drivers/iommu/intel_irq_remapping.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Applied, thanks Jan.
prev parent reply other threads:[~2014-08-19 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 11:13 [PATCH] iommu/vt-d: Don't store SIRTP request Jan Kiszka
2014-08-19 11:09 ` Joerg Roedel [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=20140819110937.GA26492@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jan.kiszka@siemens.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.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