From: Keir Fraser <keir@xensource.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 6/10] Allow vcpu to pause self
Date: Wed, 11 Jul 2007 18:02:23 +0100 [thread overview]
Message-ID: <C2BACBAF.12470%keir@xensource.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F013B1F75@pdsmsx412.ccr.corp.intel.com>
On 27/6/07 14:37, "Tian, Kevin" <kevin.tian@intel.com> wrote:
> Add self pause ability, which is required by vcpu0/dom0 when
> running on a AP. This can't be satisfied by existing interface,
> since the new flag also serves as a sync point.
>
> Signed-off-by Kevin Tian <kevin.tian@intel.com>
I think this should not be needed. Why is dom0/vcpu0 special at all? If you
are doing the final work from a softirq context, can't dom0/vcpu0 simply be
paused like all others at that point? If not then we'll need to make some
arrangement using vcpu_set_affinity() - I won't add another flag on the
context-switch path.
So currently patches 6,7,9,10 are not applied. Patches 6 & 7 because they
need more iteration, as commented above. Patches 9 & 10 will likely change
when the platform_op hypercall interface is slimmed down, so I'm leaving
them out for now.
All other patches are in (although the platform_op interface part of patch 2
is disabled).
-- Keir
next prev parent reply other threads:[~2007-07-11 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 13:37 [PATCH 6/10] Allow vcpu to pause self Tian, Kevin
2007-07-11 17:02 ` Keir Fraser [this message]
2007-07-12 2:37 ` Tian, Kevin
2007-07-12 5:05 ` Tian, Kevin
2007-07-12 6:02 ` Tian, Kevin
2007-07-12 7:41 ` Keir Fraser
2007-07-12 8:07 ` Tian, Kevin
2007-07-12 7:44 ` Keir Fraser
2007-07-12 8:01 ` Keir Fraser
2007-07-12 8:23 ` Tian, Kevin
2007-07-12 8:30 ` Keir Fraser
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=C2BACBAF.12470%keir@xensource.com \
--to=keir@xensource.com \
--cc=kevin.tian@intel.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.