All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: "Xu, Anthony" <anthony.xu@intel.com>,
	xen-devel@lists.xensource.com,
	xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] [PATCH]Make VTIdomain boot again
Date: Thu, 09 Feb 2006 08:09:08 -0700	[thread overview]
Message-ID: <1139497748.26420.240.camel@localhost> (raw)
In-Reply-To: <26F44F810A51DF42A127BC2A06BE185E03212D1A@pdsmsx404>

On Thu, 2006-02-09 at 15:07 +0800, Dong, Eddie wrote:
> Alex Williamson wrote:
> > itself.  Could we be setting some flag and adding the test to the
> > existing in_interrupt/local_softirq_pending check?  This looks rather
> > precarious.  Thanks,
> > 
> Alex:
> 	Will that be funny if we embed return_to_guest check in no
> matter in_interrupt() or local_softirq_pending() check? How about to add
> a new MACRO return_to_guest() and check in parallel with in_interrupt()
> and local_softirq_pending()?

   Yeah, that's what I was suggesting.  Thanks,

	Alex
-- 
Alex Williamson                             HP Linux & Open Source Lab

  reply	other threads:[~2006-02-09 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  7:07 [Xen-ia64-devel] [PATCH]Make VTIdomain boot again Dong, Eddie
2006-02-09 15:09 ` Alex Williamson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-10  1:23 Xu, Anthony
2006-02-09 14:33 [Xen-devel] " Dong, Eddie
2006-02-09 15:17 ` Alex Williamson
2006-02-09 15:25   ` [Xen-ia64-devel] " Keir Fraser
2006-02-09  9:32 Xu, Anthony
2006-02-09  9:50 ` Keir Fraser
2006-02-09  7:14 Xu, Anthony
2006-02-09 15:12 ` Alex Williamson
2006-02-09  2:31 Xu, Anthony
2006-02-09  3:32 ` [Xen-ia64-devel] " Alex Williamson

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=1139497748.26420.240.camel@localhost \
    --to=alex.williamson@hp.com \
    --cc=anthony.xu@intel.com \
    --cc=eddie.dong@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-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.