From: Thomas Gleixner <tglx@linutronix.de>
To: John Stoffel <john@quad.stoffel.home>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] irq/core for v6.2-rc1
Date: Mon, 12 Dec 2022 15:56:36 +0100 [thread overview]
Message-ID: <87h6y0brh7.ffs@tglx> (raw)
In-Reply-To: <Y5c1ie+VE3QS5Xhz@quad.stoffel.home>
On Mon, Dec 12 2022 at 09:07, John Stoffel wrote:
>>
>> IMS (Interrupt Message Store] is a new specification which allows device
>> manufactures to provide implementation defined storage for MSI messages
>> contrary to the uniform and specification defined storage mechanisms for
>
> This sentence reads strangley to me, I'm not quite clear on what
> "uniform and specification" really means here. Just a minor nit since
> I spent three or four re-reads trying to understand this otherwise
> really nicely written history!
Yeah, it reads a bit strange. What I wanted to say is:
IMS has an implementation defined message store while PCI/MSI[-X] has
a specified message store which is uniform accross all devices. That
uniformity allowed us to get away with "global" PCI/MSI domains.
>> The initial PCI/MSI[-X] support obviously plugged into this model which
>> resulted in some basic shared infrastructure in the PCI core code for
>> setting up MSI descriptors, which are a pure software construct for holding
>> data relevant for a particular MSI interrupt, but the actual association to
>> Linux interrupts was completely architecture specific. This model is still
>> supported today to keep museum architectures and notorious stranglers
>
> I think you mean "stragglers" not "stranglers. Though I'm sure you
> wanted to strangle things at points!
Indeed.
Thanks,
tglx
next prev parent reply other threads:[~2022-12-12 14:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 10:08 [GIT pull] x86/urgent for v6.2-rc1 Thomas Gleixner
2022-12-12 10:09 ` [GIT pull] core/debugobjects " Thomas Gleixner
2022-12-12 21:11 ` pr-tracker-bot
2022-12-12 10:09 ` [GIT pull] irq/core " Thomas Gleixner
2022-12-12 14:07 ` John Stoffel
2022-12-12 14:56 ` Thomas Gleixner [this message]
2022-12-12 21:11 ` pr-tracker-bot
2022-12-12 10:09 ` [GIT pull] smp/core " Thomas Gleixner
2022-12-12 21:11 ` pr-tracker-bot
2022-12-12 10:09 ` [GIT pull] timers/core " Thomas Gleixner
2022-12-12 21:11 ` pr-tracker-bot
2022-12-12 10:09 ` [GIT pull] x86/apic " Thomas Gleixner
2022-12-12 21:11 ` pr-tracker-bot
2022-12-12 10:09 ` [GIT pull] x86/cleanups " Thomas Gleixner
2022-12-12 21:11 ` pr-tracker-bot
2022-12-12 10:09 ` [GIT pull] x86/misc " Thomas Gleixner
2022-12-12 21:11 ` pr-tracker-bot
2022-12-12 21:11 ` [GIT pull] x86/urgent " pr-tracker-bot
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=87h6y0brh7.ffs@tglx \
--to=tglx@linutronix.de \
--cc=john@quad.stoffel.home \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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