From: "Jürgen Groß" <jgross@suse.com>
To: "Chen, Jiqian" <Jiqian.Chen@amd.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: [PATCH v3] xen: Remove dependency between pciback and privcmd
Date: Sat, 12 Oct 2024 07:48:40 +0200 [thread overview]
Message-ID: <075ce655-e871-4a3d-a550-7363bc4a165f@suse.com> (raw)
In-Reply-To: <BL1PR12MB5849C20650902FE3935BEC2AE77A2@BL1PR12MB5849.namprd12.prod.outlook.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1217 bytes --]
On 12.10.24 04:36, Chen, Jiqian wrote:
> On 2024/10/12 10:22, Chen, Jiqian wrote:
>> On 2024/10/11 20:06, Juergen Gross wrote:
>>> On 11.10.24 05:42, Jiqian Chen wrote:
>>>> Commit 2fae6bb7be32 ("xen/privcmd: Add new syscall to get gsi from dev")
>>>> adds a weak reverse dependency to the config XEN_PRIVCMD definition, that
>>>> dependency causes xen-privcmd can't be loaded on domU, because dependent
>>>> xen-pciback isn't always be loaded successfully on domU.
>>>>
>>>> To solve above problem, remove that dependency, and do not call
>>>> pcistub_get_gsi_from_sbdf() directly, instead add a hook in
>>>> drivers/xen/apci.c, xen-pciback register the real call function, then in
>>>> privcmd_ioctl_pcidev_get_gsi call that hook.
>>>>
>>>> Fixes: 2fae6bb7be32 ("xen/privcmd: Add new syscall to get gsi from dev")
>>>> Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
>>>> Signed-off-by: Jiqian Chen <Jiqian.Chen@amd.com>
>>>
>>> Unfortunately I'm seeing a build breakage for the 32-bit x86 build.
> Could you please attach the link or steps?
> Then I can reproduce it, and validate it locally with new changes.
I'm using the attached kernel config.
Juergen
[-- Attachment #1.1.2: .config --]
[-- Type: application/x-config, Size: 144408 bytes --]
[-- Attachment #1.1.3: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 491 bytes --]
next prev parent reply other threads:[~2024-10-12 5:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 3:42 Jiqian Chen
2024-10-11 8:54 ` Jan Beulich
2024-10-11 9:20 ` Chen, Jiqian
2024-10-11 9:33 ` Chen, Jiqian
2024-10-11 10:10 ` Jan Beulich
2024-10-11 11:12 ` Juergen Gross
2024-10-11 11:16 ` Juergen Gross
2024-10-11 12:06 ` Juergen Gross
2024-10-12 2:22 ` Chen, Jiqian
2024-10-12 2:36 ` Chen, Jiqian
2024-10-12 5:48 ` Jürgen Groß [this message]
2024-10-12 6:50 ` Chen, Jiqian
2024-10-12 8:28 ` Jürgen Groß
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=075ce655-e871-4a3d-a550-7363bc4a165f@suse.com \
--to=jgross@suse.com \
--cc=Jiqian.Chen@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=oleksandr_tyshchenko@epam.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
all inboxes | Powered by JetHome®