From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: elena.ufimtseva@oracle.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
dario.faggioli@citrix.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org, keir@xen.org, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v7 2/5] sysctl: Add sysctl interface for querying PCI topology
Date: Tue, 21 Apr 2015 09:13:09 -0400 [thread overview]
Message-ID: <55364CE5.4050602@oracle.com> (raw)
In-Reply-To: <55364D38.3020203@citrix.com>
On 04/21/2015 09:14 AM, Andrew Cooper wrote:
> On 21/04/15 13:56, Boris Ostrovsky wrote:
>> On 04/21/2015 03:01 AM, Jan Beulich wrote:
>>>>>> --- a/docs/misc/xsm-flask.txt
>>>>>> +++ b/docs/misc/xsm-flask.txt
>>>>>> @@ -121,6 +121,7 @@ __HYPERVISOR_sysctl (xen/include/public/sysctl.h)
>>>>>> * XEN_SYSCTL_cpupool_op
>>>>>> * XEN_SYSCTL_scheduler_op
>>>>>> * XEN_SYSCTL_coverage_op
>>>>>> + * XEN_SYSCTL_pcitopoinfo
>>> No additions to this list are permitted. Either the new sub-op is
>>> disaggregation safe (which it looks to be), or it can't be accepted.
>> True, it *is* safe, but why then cputopoinfo and numainfo are in this
>> list? They look to be safe as well.
> This list includes "not yet audited". It is quite likely that some
> entries in the list are safe.
>
> fwiw, neither cputopo nor numainfo are currently safe for very large
> systems.
Why would safety of an operation depend on system size? And how are
these two unsafe? (Because maybe then PCI topology query is unsafe in
the same manner)
-boris
-boris
next prev parent reply other threads:[~2015-04-21 13:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 16:59 [PATCH v7 0/5] Display IO topology when PXM data is available (plus some cleanup) Boris Ostrovsky
2015-04-17 16:59 ` [PATCH v7 1/5] sysctl: Make XEN_SYSCTL_numainfo a little more efficient Boris Ostrovsky
2015-04-17 17:14 ` Andrew Cooper
2015-04-17 16:59 ` [PATCH v7 2/5] sysctl: Add sysctl interface for querying PCI topology Boris Ostrovsky
2015-04-17 17:16 ` Andrew Cooper
2015-04-21 7:01 ` Jan Beulich
2015-04-21 12:56 ` Boris Ostrovsky
2015-04-21 13:14 ` Andrew Cooper
2015-04-21 13:13 ` Boris Ostrovsky [this message]
2015-04-21 13:30 ` Andrew Cooper
2015-04-21 13:18 ` Jan Beulich
2015-04-23 22:20 ` Boris Ostrovsky
2015-04-24 7:19 ` Jan Beulich
2015-04-24 14:09 ` Boris Ostrovsky
2015-04-24 17:42 ` Boris Ostrovsky
2015-05-01 13:56 ` Ian Campbell
2015-05-01 15:20 ` Boris Ostrovsky
2015-05-01 15:31 ` Ian Campbell
2015-04-17 16:59 ` [PATCH v7 3/5] libxl/libxc: Move libxl_get_cpu_topology()'s hypercall buffer management to libxc Boris Ostrovsky
2015-04-17 16:59 ` [PATCH v7 4/5] libxl/libxc: Move libxl_get_numainfo()'s " Boris Ostrovsky
2015-04-17 16:59 ` [PATCH v7 5/5] libxl: Add interface for querying hypervisor about PCI topology Boris Ostrovsky
2015-04-21 11:27 ` Ian Campbell
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=55364CE5.4050602@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=elena.ufimtseva@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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 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.