From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Jacek Konieczny <jajcus@jajcus.net>
Cc: IanJackson <Ian.Jackson@eu.citrix.com>,
Mariusz Mazur <mmazur@axeos.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [BUG] libxenstat and xentop confused by renamed VIF interfaces
Date: Wed, 21 May 2014 15:01:14 +0100 [thread overview]
Message-ID: <537CCDCA02000078000148FF@mail.emea.novell.com> (raw)
In-Reply-To: <1400673169.4856.26.camel@kazak.uk.xensource.com>
>>> On 21.05.14 at 13:52, <Ian.Campbell@citrix.com> wrote:
> On Wed, 2014-05-21 at 13:35 +0200, Jacek Konieczny wrote:
>> One question: can I assume /sys is always mounted and the
>> '/sys/.../device/nodename', contains 'backend/vif/$domid/*' or should
>> there be a fall-back to the old behaviour?
>
> I think on Linux we can assume these days that /sys must exist. I'm less
> sure about the content of nodename, in particular WRT the behaviour of
> the classic-Xen forward ports. (Jan, CCd, might know).
>
> I'd be inclined to keep the existing code as a fallback for now, I
> think.
I agree - an eventual change in sysfs layout would need hunting
down between 2.6.18 and 3.15; not something I would do without
a very good reason. And I can't tell without doing so...
Jan
prev parent reply other threads:[~2014-05-21 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 7:52 [BUG] libxenstore and xentop confused by renamed VIF interfaces Jacek Konieczny
2014-05-21 8:15 ` [BUG] libxenstat " Jacek Konieczny
2014-05-21 10:29 ` [BUG] libxenstore " Ian Campbell
2014-05-21 10:48 ` [BUG] libxenstat " Jacek Konieczny
2014-05-21 10:53 ` Ian Campbell
2014-05-21 11:35 ` Jacek Konieczny
2014-05-21 11:52 ` Ian Campbell
2014-05-21 14:01 ` Jan Beulich [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=537CCDCA02000078000148FF@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jajcus@jajcus.net \
--cc=mmazur@axeos.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).