From: Roger Pau Monne <roger.pau@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH for-4.13 0/2] x86/ioapic: fix clear_IO_APIC_pin when using interrupt remapping
Date: Thu, 7 Nov 2019 16:06:07 +0100 [thread overview]
Message-ID: <20191107150609.93004-1-roger.pau@citrix.com> (raw)
Hello,
Current code in clear_IO_APIC_pin doesn't properly deal with IO-APIC
entries already configured to point to entries in the iommu interrupt
remapping table, fix this.
Roger Pau Monne (2):
x86/ioapic: remove usage of TRUE and FALSE in clear_IO_APIC_pin
x86/ioapic: don't use raw entry reads/writes in clear_IO_APIC_pin
xen/arch/x86/io_apic.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
2.23.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-11-07 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 15:06 Roger Pau Monne [this message]
2019-11-07 15:06 ` [Xen-devel] [PATCH for-4.13 1/2] x86/ioapic: remove usage of TRUE and FALSE in clear_IO_APIC_pin Roger Pau Monne
2019-11-07 15:13 ` Andrew Cooper
2019-11-07 15:20 ` Jan Beulich
2019-11-07 15:06 ` [Xen-devel] [PATCH for-4.13 2/2] x86/ioapic: don't use raw entry reads/writes " Roger Pau Monne
2019-11-07 15:28 ` Jan Beulich
2019-11-07 15:46 ` Roger Pau Monné
2019-11-07 15:51 ` Roger Pau Monné
2019-11-07 15:56 ` Jan Beulich
2019-11-08 9:27 ` Roger Pau Monné
2019-11-08 10:16 ` Jan Beulich
2019-11-08 16:07 ` Roger Pau Monné
2019-11-08 16:51 ` Jan Beulich
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=20191107150609.93004-1-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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.