From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "David Woodhouse" <dwmw2@infradead.org>,
"Roger Pau Monne" <roger.pau@citrix.com>,
<xen-devel@lists.xenproject.org>
Cc: "Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Willi Junga" <xenproject@ymy.be>
Subject: Re: [PATCH] x86/io-apic: fix directed EOI when using AMd-Vi interrupt remapping
Date: Mon, 21 Oct 2024 13:18:06 +0100 [thread overview]
Message-ID: <D51H7ZKHDY49.1NG4YOYCBIX96@cloud.com> (raw)
In-Reply-To: <52c88b22daeb3740402f478ca393e07d84c87731.camel@infradead.org>
On Mon Oct 21, 2024 at 12:32 PM BST, David Woodhouse wrote:
> On Mon, 2024-10-21 at 10:55 +0100, Alejandro Vallejo wrote:
> > On Fri Oct 18, 2024 at 9:08 AM BST, Roger Pau Monne wrote:
> > > When using AMD-VI interrupt remapping the vector field in the IO-APIC RTE is
> > > repurposed to contain part of the offset into the remapping table. Previous to
> >
> > For my own education....
>
> Careful what you wish for.
>
> http://david.woodhou.se/more-than-you-ever-wanted-to-know-about-x86-msis.txt
I had seen it before, but then neglected to give it the attentive read it very
much deserves. Let me correct that, thanks.
Cheers,
Alejandro
next prev parent reply other threads:[~2024-10-21 12:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 8:08 [PATCH] x86/io-apic: fix directed EOI when using AMd-Vi interrupt remapping Roger Pau Monne
2024-10-19 3:23 ` Marek Marczykowski-Górecki
2024-10-21 11:43 ` Woodhouse, David
2024-11-02 3:54 ` marmarek
2024-10-21 9:55 ` Alejandro Vallejo
2024-10-21 10:07 ` Andrew Cooper
2024-10-21 10:49 ` Roger Pau Monné
2024-10-21 11:32 ` David Woodhouse
2024-10-21 12:18 ` Alejandro Vallejo [this message]
2024-10-21 9:56 ` Alejandro Vallejo
2024-10-21 11:10 ` Andrew Cooper
2024-10-21 11:38 ` Andrew Cooper
2024-10-21 11:49 ` [EXTERNAL] " David Woodhouse
2024-10-21 11:53 ` Andrew Cooper
2024-10-21 12:02 ` David Woodhouse
2024-10-21 14:25 ` Roger Pau Monné
2024-10-21 14:03 ` Roger Pau Monné
2024-10-21 17:00 ` Roger Pau Monné
2024-10-21 17:21 ` Andrew Cooper
2024-10-21 11:57 ` Roger Pau Monné
2024-10-21 12:33 ` Andrew Cooper
2024-10-28 11:02 ` Jan Beulich
2024-10-28 11:05 ` Jan Beulich
2024-10-29 15:56 ` Jan Beulich
2024-10-21 11:34 ` David Woodhouse
2024-10-21 14:06 ` Roger Pau Monné
2024-10-21 14:51 ` Andrew Cooper
2024-10-21 14:54 ` David Woodhouse
2024-10-21 15:00 ` Roger Pau Monné
2024-10-21 15:03 ` Alejandro Vallejo
2024-10-21 15:08 ` Andrew Cooper
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=D51H7ZKHDY49.1NG4YOYCBIX96@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw2@infradead.org \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xenproject@ymy.be \
/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.