All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "Jürgen Groß" <jgross@suse.com>, xen-devel@lists.xen.org
Subject: Re: how to assign resources exclusive to a single domU
Date: Fri, 27 Feb 2015 10:24:11 +0000	[thread overview]
Message-ID: <1425032651.14641.148.camel@citrix.com> (raw)
In-Reply-To: <20150227081900.GA10392@aepfle.de>

On Fri, 2015-02-27 at 09:19 +0100, Olaf Hering wrote:
> On Fri, Feb 27, Jürgen Groß wrote:
> 
> > On 02/26/2015 09:57 AM, Olaf Hering wrote:
> > >I wonder what should be done in my changes for libxl.
> > If you are doing something, please add a flag to be able to disable
> > the additional security checks regarding multiple assignment.
> 
> I think libxl should just allow multiple assignments of physical
> devices. Its up to the admin to make sure the overall config is sane.

I can't remember what libxl does today but WRT disks (with the phy
backend at least) xend used to have sharing checks and refuse to allow
sharing (for writeable disks) unless overridden (by "w+" in the mode
string, IIRC).

I don't think libxl implements those checks, so the override isn't
supported, but maybe it would be good to do so, and maybe it would be a
good idea for pvscsi to at least be consistent with what we might
eventually do for disks?

(FWIW I think most of the checks were actually in the block-* scripts,
I'm not sure why they are active under libxl)

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2015-02-27 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  8:57 how to assign resources exclusive to a single domU Olaf Hering
2015-02-27  4:53 ` Jürgen Groß
2015-02-27  8:19   ` Olaf Hering
2015-02-27 10:24     ` Ian Campbell [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=1425032651.14641.148.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=jgross@suse.com \
    --cc=olaf@aepfle.de \
    --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.