All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	xen-devel@lists.xenproject.org,
	Anthony PERARD <anthony.perard@vates.tech>
Subject: Re: [PATCH 2/4] stubdom: remove pciutils
Date: Wed, 19 Aug 2026 09:12:00 +0200	[thread overview]
Message-ID: <ab78351b-6b03-407c-9bcd-74b1566fd853@suse.com> (raw)
In-Reply-To: <aoTRyxN4gzsEwJa5@end>


[-- Attachment #1.1.1: Type: text/plain, Size: 1918 bytes --]

On 18.08.26 23:42, Samuel Thibault wrote:
> Jürgen Groß, le mar. 18 août 2026 07:43:34 +0200, a ecrit:
>> On 17.08.26 18:37, Samuel Thibault wrote:
>>> Juergen Gross, le lun. 17 août 2026 10:24:02 +0200, a ecrit:
>>>> On 17.08.26 09:48, Samuel Thibault wrote:
>>>>> Juergen Gross, le lun. 17 août 2026 09:18:41 +0200, a ecrit:
>>>>>> There is no user of libpci left in stubdoms.
>>>>>>
>>>>>> Remove libpci from the stubdom build system.
>>>>>
>>>>> Wouldn't it be useful to keep this for anybody who would want to drive a
>>>>> PCI card from a stubdomain?
>>>>>
>>>>> I mean, in the zlib case, it's really a mere question of build & link,
>>>>> so we don't need to ship it, people can do it themselves easily like for
>>>>> any other library.
>>>>>
>>>>> But here there is actual porting work, that we'd better not lose but
>>>>> keep shipping.
>>>>
>>>> This is all still available via git.
>>>
>>> No, it is not really.
>>>
>>> I keep reading this argument, but people will not know that something
>>> exists in the git history, and will just assume that it does not exist
>>> and has to be written.
>>
>> What about adding a comment to the stubdom Makefile in a separate patch, like:
>>
>> # pciutils support has been removed with commit <commit-id>, revert that patch
>> # in case it is needed again.
>>
>> I think this would be preferable over unused and probably bit-rotten code in
>> the repository.
> 
> I don't see why it would be bit-rotten, since the pciutils version in
> used is fixed, it's a library that has a quite stable API, and the pci
> xen interface is supposed to keep backward compatibility.

Then I'd rather add it to Mini-OS (probably behind another CONFIG option) than
having it in the Xen tree.

This way it could be test-built much easier with Mini-OS, thus avoiding any
breakage in case e.g. a pcifront interface is changed.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  parent reply	other threads:[~2026-08-19  7:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  7:18 [PATCH 0/4] stubdom: remove building unused libraries Juergen Gross
2026-08-17  7:18 ` [PATCH 1/4] Config: update Mini-OS commit id Juergen Gross
2026-08-17  7:56   ` Jan Beulich
2026-08-17  7:18 ` [PATCH 2/4] stubdom: remove pciutils Juergen Gross
2026-08-17  7:48   ` Samuel Thibault
2026-08-17  8:24     ` Juergen Gross
2026-08-17 16:37       ` Samuel Thibault
2026-08-18  5:43         ` Jürgen Groß
2026-08-18 21:42           ` Samuel Thibault
2026-08-19  6:40             ` Jan Beulich
2026-08-19  7:12             ` Jürgen Groß [this message]
2026-08-18  6:03         ` Jan Beulich
2026-08-18 21:40           ` Samuel Thibault
2026-08-19  6:36             ` Jan Beulich
2026-08-20  0:17               ` Samuel Thibault
2026-08-19  7:05             ` Jürgen Groß
2026-08-17  7:18 ` [PATCH 3/4] stubdom: remove build of zlib Juergen Gross
2026-08-17  7:30   ` Samuel Thibault
2026-08-17  7:18 ` [PATCH 4/4] CHANGELOG: add removal of grub-pv Juergen Gross

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=ab78351b-6b03-407c-9bcd-74b1566fd853@suse.com \
    --to=jgross@suse.com \
    --cc=anthony.perard@vates.tech \
    --cc=samuel.thibault@ens-lyon.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 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.