All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Steve Ofsthun <sofsthun@virtualiron.com>
Cc: xen-devel@lists.xensource.com, Mats@us.ibm.com, Petersson@linux.ibm.com
Subject: Re: [RFC] Hypercalls from HVM guests
Date: Fri, 07 Apr 2006 15:22:27 -0500	[thread overview]
Message-ID: <4436CA03.7050509@us.ibm.com> (raw)
In-Reply-To: <4436BDE2.5090504@virtualiron.com>

Steve Ofsthun wrote:
> Petersson, Mats wrote:
>
>
> This sounds like a simple to use method for communicating with the HVM 
> code,
> but I would like to gracefully detect native execution and print a useful
> error message at module load time.  Recovering from a native mode 
> exception
> will be very O/S specific (if allowed at all).

PIO is probably a bit safer.  PIO probing, while a bit ugly, is 
certainly frequently used.

Plus, PIO instructions are not sensitive (whereas CPUID is) which means 
that it can also be used as a mechanism for non-HVM guests.

Regards,

Anthony Liguori

>> Actually, maybe using an unused index for CPUID (e.g. 0xb0000000) would
>> be better? As that's defined to return all zero's, and not cause any
>> traps whatever value you use (unless the CPU is so old that it doesn't
>> support CPUID, of course).
>
> This sounds encouraging, but is CPUID always trapped by the HVM code?
>
> Steve

  reply	other threads:[~2006-04-07 20:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 17:56 [RFC] Hypercalls from HVM guests Petersson, Mats
2006-04-07 19:30 ` Steve Ofsthun
2006-04-07 20:22   ` Anthony Liguori [this message]
2006-04-08  7:31   ` Keir Fraser
2006-04-08 14:12     ` Andi Kleen
2006-04-08 15:05       ` Keir Fraser
2006-04-12 15:39         ` Stephen C. Tweedie
2006-04-12 17:05           ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2006-04-09 15:08 Nakajima, Jun
2006-04-09 13:56 Nakajima, Jun
2006-04-09 14:09 ` Keir Fraser
2006-04-12 15:58 ` Stephen C. Tweedie
2006-04-08 23:33 Nakajima, Jun
2006-04-09  7:56 ` Keir Fraser
2006-04-07 17:24 Petersson, Mats
2006-04-07 17:40 ` Keir Fraser
2006-04-07  8:47 Petersson, Mats
2006-04-07 17:06 ` Steve Ofsthun
2006-04-07  2:32 Yu, Ke
2006-04-06 21:10 Steve Ofsthun

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=4436CA03.7050509@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Mats@us.ibm.com \
    --cc=Petersson@linux.ibm.com \
    --cc=sofsthun@virtualiron.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.