All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: rendezvousing all physical CPUs
Date: Fri, 01 Dec 2006 09:11:17 +0000	[thread overview]
Message-ID: <C195A235.558A%keir@xensource.com> (raw)
In-Reply-To: <456FF2F8.76E4.0078.0@novell.com>

On 1/12/06 08:16, "Jan Beulich" <jbeulich@novell.com> wrote:

>> How about providing the linear address of a chunk of dom0 code that Xen
>> should run in ring 0 with CPUs in a particular configuration? We could
>> provide flags to represent useful configurations: e.g., run on all CPUs
>> atomicaly, run on CPU0 only and quiesce others, etc.
> 
> Hmm??? I would have to question why dom0 currently gets run in ring 1 then.

Uniformity with execution of other domains and it's also a useful safety
mechanism for catching dom0 bugs. It is *not* for security reasons!

> I would at best consider allowing the guest to pass a batch of operations that
> it wants carried out - I/O memory accesses (normal RAM not allowed), MSR
> reads/writes, port I/O. However, for the specific case of the RNG, PCI config
> space accesses would also need to be supported - while they can be reduced
> to iomem or port accesses, abstracting this out from the requester and from
> Xen would require some thought.

Dom0 can map any memory, DMA to any memory, and with your original proposed
hypercall would be able to tear down physical CPUs for unbounded time
periods. It 0wns the machine already. ;-)

 -- Keir

      reply	other threads:[~2006-12-01  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 16:14 rendezvousing all physical CPUs Jan Beulich
2006-11-30 16:19 ` ron minnich
2006-11-30 16:32   ` Jan Beulich
2006-11-30 16:33     ` ron minnich
2006-11-30 16:55 ` Keir Fraser
2006-11-30 17:12   ` ron minnich
2006-11-30 17:20     ` Keir Fraser
2006-12-01  8:16   ` Jan Beulich
2006-12-01  9:11     ` Keir Fraser [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=C195A235.558A%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /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.