public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Chen, Jiqian" <Jiqian.Chen@amd.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	"Len Brown" <lenb@kernel.org>, "Juergen Gross" <jgross@suse.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"Hildebrand, Stewart" <Stewart.Hildebrand@amd.com>,
	"Huang, Ray" <Ray.Huang@amd.com>,
	"Ragiadakou, Xenia" <Xenia.Ragiadakou@amd.com>
Subject: Re: [RFC KERNEL PATCH v4 3/3] PCI/sysfs: Add gsi sysfs for pci_dev
Date: Tue, 23 Jan 2024 10:02:52 -0600	[thread overview]
Message-ID: <20240123160252.GA316914@bhelgaas> (raw)
In-Reply-To: <BL1PR12MB5849D7A9EC2BEB55CAF3A889E7742@BL1PR12MB5849.namprd12.prod.outlook.com>

On Tue, Jan 23, 2024 at 10:13:52AM +0000, Chen, Jiqian wrote:
> On 2024/1/23 07:37, Bjorn Helgaas wrote:
> > On Fri, Jan 05, 2024 at 02:22:17PM +0800, Jiqian Chen wrote:
> >> There is a need for some scenarios to use gsi sysfs.
> >> For example, when xen passthrough a device to dumU, it will
> >> use gsi to map pirq, but currently userspace can't get gsi
> >> number.
> >> So, add gsi sysfs for that and for other potential scenarios.
> ...

> > I don't know enough about Xen to know why it needs the GSI in
> > userspace.  Is this passthrough brand new functionality that can't be
> > done today because we don't expose the GSI yet?
>
> In Xen architecture, there is a privileged domain named Dom0 that
> has ACPI support and is responsible for detecting and controlling
> the hardware, also it performs privileged operations such as the
> creation of normal (unprivileged) domains DomUs. When we give to a
> DomU direct access to a device, we need also to route the physical
> interrupts to the DomU. In order to do so Xen needs to setup and map
> the interrupts appropriately.

What kernel interfaces are used for this setup and mapping?

  reply	other threads:[~2024-01-23 16:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05  6:22 [RFC KERNEL PATCH v4 0/3] Support device passthrough when dom0 is PVH on Xen Jiqian Chen
2024-01-05  6:22 ` [RFC KERNEL PATCH v4 1/3] xen/pci: Add xen_reset_device_state function Jiqian Chen
2024-02-23  0:18   ` Stefano Stabellini
2024-01-05  6:22 ` [RFC KERNEL PATCH v4 2/3] xen/pvh: Setup gsi for passthrough device Jiqian Chen
2024-02-23  0:23   ` Stefano Stabellini
2024-02-23  6:08     ` Chen, Jiqian
2024-01-05  6:22 ` [RFC KERNEL PATCH v4 3/3] PCI/sysfs: Add gsi sysfs for pci_dev Jiqian Chen
2024-01-22  6:36   ` Chen, Jiqian
2024-01-22 23:37   ` Bjorn Helgaas
2024-01-23 10:13     ` Chen, Jiqian
2024-01-23 16:02       ` Bjorn Helgaas [this message]
2024-01-25  7:17         ` Chen, Jiqian
2024-01-29 22:01           ` Bjorn Helgaas
2024-01-30  9:07             ` Roger Pau Monné
2024-01-30 20:44               ` Bjorn Helgaas
2024-01-31  8:58                 ` Roger Pau Monné
2024-01-31 19:00                   ` Bjorn Helgaas
2024-02-01  8:39                     ` Roger Pau Monné
2024-02-09 21:05                       ` Bjorn Helgaas
2024-02-12  9:13                         ` Roger Pau Monné
2024-02-12 19:18                           ` Bjorn Helgaas
2024-02-15  8:37                             ` Roger Pau Monné
2024-03-01  7:57                               ` Chen, Jiqian
2024-04-08  6:42                                 ` Chen, Jiqian
2024-04-09 20:03                                   ` Bjorn Helgaas

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=20240123160252.GA316914@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Jiqian.Chen@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=Stewart.Hildebrand@amd.com \
    --cc=Xenia.Ragiadakou@amd.com \
    --cc=bhelgaas@google.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=rafael@kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox