From: "Jürgen Groß" <jgross@suse.com>
To: David Miller <davem@davemloft.net>, pdurrant@amazon.com
Cc: xen-devel@lists.xenproject.org, wei.liu@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH net-next] xen-netback: get rid of old udev related code
Date: Fri, 13 Dec 2019 06:40:38 +0100 [thread overview]
Message-ID: <cefcf3a4-fc10-d62a-cac9-81f0e47710a8@suse.com> (raw)
In-Reply-To: <20191212.110513.1770889236741616001.davem@davemloft.net>
On 12.12.19 20:05, David Miller wrote:
> From: Paul Durrant <pdurrant@amazon.com>
> Date: Thu, 12 Dec 2019 13:54:06 +0000
>
>> In the past it used to be the case that the Xen toolstack relied upon
>> udev to execute backend hotplug scripts. However this has not been the
>> case for many releases now and removal of the associated code in
>> xen-netback shortens the source by more than 100 lines, and removes much
>> complexity in the interaction with the xenstore backend state.
>>
>> NOTE: xen-netback is the only xenbus driver to have a functional uevent()
>> method. The only other driver to have a method at all is
>> pvcalls-back, and currently pvcalls_back_uevent() simply returns 0.
>> Hence this patch also facilitates further cleanup.
>>
>> Signed-off-by: Paul Durrant <pdurrant@amazon.com>
>
> If userspace ever used this stuff, I seriously doubt you can remove this
> even if it hasn't been used in 5+ years.
Hmm, depends.
This has been used by Xen tools in dom0 only. If the last usage has been
in a Xen version which is no longer able to run with current Linux in
dom0 it could be removed. But I guess this would have to be a rather old
version of Xen (like 3.x?).
Paul, can you give a hint since which Xen version the toolstack no
longer relies on udev to start the hotplug scripts?
Juergen
WARNING: multiple messages have this Message-ID (diff)
From: "Jürgen Groß" <jgross@suse.com>
To: David Miller <davem@davemloft.net>, pdurrant@amazon.com
Cc: xen-devel@lists.xenproject.org, wei.liu@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH net-next] xen-netback: get rid of old udev related code
Date: Fri, 13 Dec 2019 06:40:38 +0100 [thread overview]
Message-ID: <cefcf3a4-fc10-d62a-cac9-81f0e47710a8@suse.com> (raw)
In-Reply-To: <20191212.110513.1770889236741616001.davem@davemloft.net>
On 12.12.19 20:05, David Miller wrote:
> From: Paul Durrant <pdurrant@amazon.com>
> Date: Thu, 12 Dec 2019 13:54:06 +0000
>
>> In the past it used to be the case that the Xen toolstack relied upon
>> udev to execute backend hotplug scripts. However this has not been the
>> case for many releases now and removal of the associated code in
>> xen-netback shortens the source by more than 100 lines, and removes much
>> complexity in the interaction with the xenstore backend state.
>>
>> NOTE: xen-netback is the only xenbus driver to have a functional uevent()
>> method. The only other driver to have a method at all is
>> pvcalls-back, and currently pvcalls_back_uevent() simply returns 0.
>> Hence this patch also facilitates further cleanup.
>>
>> Signed-off-by: Paul Durrant <pdurrant@amazon.com>
>
> If userspace ever used this stuff, I seriously doubt you can remove this
> even if it hasn't been used in 5+ years.
Hmm, depends.
This has been used by Xen tools in dom0 only. If the last usage has been
in a Xen version which is no longer able to run with current Linux in
dom0 it could be removed. But I guess this would have to be a rather old
version of Xen (like 3.x?).
Paul, can you give a hint since which Xen version the toolstack no
longer relies on udev to start the hotplug scripts?
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-13 5:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 13:54 [PATCH net-next] xen-netback: get rid of old udev related code Paul Durrant
2019-12-12 13:54 ` [Xen-devel] " Paul Durrant
2019-12-12 16:31 ` Jason Andryuk
2019-12-12 16:31 ` Jason Andryuk
2019-12-12 16:45 ` Durrant, Paul
2019-12-12 16:45 ` Durrant, Paul
2019-12-12 19:05 ` David Miller
2019-12-12 19:05 ` [Xen-devel] " David Miller
2019-12-13 5:40 ` Jürgen Groß [this message]
2019-12-13 5:40 ` Jürgen Groß
2019-12-13 9:24 ` Durrant, Paul
2019-12-13 9:24 ` Durrant, Paul
2019-12-13 10:02 ` Jürgen Groß
2019-12-13 10:02 ` Jürgen Groß
2019-12-13 10:12 ` Durrant, Paul
2019-12-13 10:12 ` Durrant, Paul
2019-12-16 8:10 ` Jürgen Groß
2019-12-16 8:10 ` Jürgen Groß
2019-12-16 8:18 ` Durrant, Paul
2019-12-16 8:18 ` Durrant, Paul
2019-12-16 8:29 ` Jürgen Groß
2019-12-16 8:29 ` Jürgen Groß
2020-01-09 13:55 ` Rich Persaud
2020-01-09 13:55 ` Rich Persaud
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=cefcf3a4-fc10-d62a-cac9-81f0e47710a8@suse.com \
--to=jgross@suse.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pdurrant@amazon.com \
--cc=wei.liu@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 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.