From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Ian Jackson" <ian.jackson@eu.citrix.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] systemd: drop dependency on proc-xen.mount in xendriverdomain.service
Date: Mon, 25 Jul 2016 10:49:32 +0100 [thread overview]
Message-ID: <20160725094932.GH1008@citrix.com> (raw)
In-Reply-To: <d27e7d91-8fdc-84ce-6baf-275048bd2247@citrix.com>
On Mon, Jul 25, 2016 at 10:45:54AM +0100, Andrew Cooper wrote:
> On 25/07/16 10:34, Wei Liu wrote:
> > On Mon, Jul 25, 2016 at 11:30:32AM +0200, Marek Marczykowski-Górecki wrote:
> >> On Mon, Jul 25, 2016 at 10:27:47AM +0100, Wei Liu wrote:
> >>> On Sun, Jul 24, 2016 at 09:27:13PM +0200, Marek Marczykowski-Górecki wrote:
> >>>> It is no longer required since xl devd use /dev/xen interface.
> >>>>
> >>> How would this unit work when there is no /dev/xen interface?
> >> Does it happen in reality? I thought /proc/xen is deprecated for a long
> >> time...
>
> It really should be, but isn't.
>
> /proc/xen/capabilities and /proc/xen/allsyms (?) don't have any
> equivalent in /dev/
>
> >>
> > I can't tell whether it happens in reality or not. I also hope to get
> > rid of deprecated interface but they are here to stay for as long as it
> > takes.
> >
> > I guess the question is, do you have a compelling reason against keeping
> > this dependency?
>
> We really should be making xenfs deprecated and able to be compiled out
> of Linux. It is a hangover of the early classic kernels which isn't
> necessary, and causes subtle/weird failures if it isn't mounted.
>
+1 from me of course!
When the kernel is ready, I shall remove the fallback in libraries and
then we can remove all references to proc-xen.mount and even
proc-xen.mount itself.
Wei.
> ~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-25 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1469388272-22789-1-git-send-email-marmarek@invisiblethingslab.com>
2016-07-24 19:27 ` [PATCH 2/2] systemd: drop dependency on proc-xen.mount in xendriverdomain.service Marek Marczykowski-Górecki
2016-07-25 9:27 ` Wei Liu
2016-07-25 9:30 ` Marek Marczykowski-Górecki
2016-07-25 9:34 ` Wei Liu
2016-07-25 9:40 ` Marek Marczykowski-Górecki
2016-07-25 9:45 ` Andrew Cooper
2016-07-25 9:49 ` Wei Liu [this message]
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=20160725094932.GH1008@citrix.com \
--to=wei.liu2@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).