From: "H. Peter Anvin" <hpa@zytor.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PING^3][RESEND^3][PATCH v3] x86/PCI: Add support for the Intel 82378ZB/82379AB (SIO/SIO.A) PIRQ router
Date: Wed, 01 Mar 2023 09:16:54 -0800 [thread overview]
Message-ID: <66DC3D77-91AC-4F1B-BE3E-892A9B9980BC@zytor.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2303011311540.57556@angie.orcam.me.uk>
On March 1, 2023 5:14:59 AM PST, "Maciej W. Rozycki" <macro@orcam.me.uk> wrote:
>On Sun, 8 Jan 2023, Maciej W. Rozycki wrote:
>
>> The Intel 82378ZB System I/O (SIO) and 82379AB System I/O APIC (SIO.A)
>> ISA bridges implement PCI interrupt steering with a PIRQ router[1][2]
>> that is exactly the same as that of the PIIX and ICH southbridges (or
>> actually the other way round, given that the SIO ASIC was there first).
>
> Ping for:
><https://lore.kernel.org/lkml/alpine.DEB.2.21.2301081956290.65308@angie.orcam.me.uk/>.
>
> I think the patch is fairly obvious. Are there any outstanding concerns
>that prevent it from being applied?
>
> Maciej
>
Has this patch been actually tested on a real machine, or is it purely theoretical?
next prev parent reply other threads:[~2023-03-01 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 19:59 [RESEND^3][PATCH " Maciej W. Rozycki
2023-01-30 21:42 ` [PING][RESEND^3][PATCH " Maciej W. Rozycki
2023-02-12 23:17 ` [PING^2][RESEND^3][PATCH " Maciej W. Rozycki
2023-03-01 13:14 ` [PING^3][RESEND^3][PATCH " Maciej W. Rozycki
2023-03-01 17:16 ` H. Peter Anvin [this message]
2023-03-01 18:01 ` Maciej W. Rozycki
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=66DC3D77-91AC-4F1B-BE3E-892A9B9980BC@zytor.com \
--to=hpa@zytor.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®