All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Kaushik Barde <Kaushik_Barde@Phoenix.com>,
	Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: EPS Signature
Date: Mon, 12 Feb 2007 07:43:39 +0000	[thread overview]
Message-ID: <C1F5CB2B.1863%Keir.Fraser@cl.cam.ac.uk> (raw)
In-Reply-To: <0EF82802ABAA22479BC1CE8E2F60E8C30164B688@scl-exch2k3.phoenix.com>


It doesn't appear obviously incorrect.

 K.


On 12/2/07 02:36, "Kaushik Barde" <Kaushik_Barde@Phoenix.com> wrote:

> 
> 
> But is the usage HYPERVISOR_update_descriptor(...) appropriate?
> 
> -Kaushik
> 
> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
> Sent: Sunday, February 11, 2007 4:58 PM
> To: Kaushik Barde; Ian Pratt; Xen devel list
> Subject: Re: [Xen-devel] EPS Signature
> 
> On 11/2/07 23:39, "Kaushik Barde" <Kaushik_Barde@Phoenix.com> wrote:
> 
>> gdt_table  = get_cpu_gdt_table(cpu);
>> l_entry_ma = virt_to_bus(&(gdt_table[l_Request.entryNum]));
>> l_desc_64  = *( (u64 *) &l_Desc);
> 
> This should be fine, assuming gdt_table is a normal kernel virtual
> address
> (e.g., returned by kmalloc()). I/O memory is a different matter in Xen,
> in
> that virt_to_bus() won't work. In fact the same restriction holds in
> native
> Linux as well (I/O memory shouldn't be virt_to_bus()ed).
> 
>  -- Keir
> 
> 

  reply	other threads:[~2007-02-12  7:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 13:53 xensource (pci) device id's? Gerd Hoffmann
2007-02-01 13:58 ` Ian Campbell
2007-02-01 14:30   ` Gerd Hoffmann
2007-02-01 15:45     ` Gerd Hoffmann
2007-02-02  9:26       ` Ian Campbell
2007-02-02  9:47         ` Gerd Hoffmann
2007-02-02 18:25       ` Keir Fraser
2007-02-05  8:48         ` Gerd Hoffmann
2007-02-05 14:20         ` Gerd Hoffmann
2007-02-02 19:03       ` Keir Fraser
2007-02-05  2:29         ` EPS Signature Kaushik Barde
2007-02-05  2:52           ` Ian Pratt
2007-02-10  7:52             ` GDT access from DOM-0 driver Kaushik Barde
2007-02-11  1:33             ` EPS Signature Kaushik Barde
2007-02-11 10:09               ` Keir Fraser
2007-02-11 23:39                 ` Kaushik Barde
2007-02-12  0:58                   ` Keir Fraser
2007-02-12  2:36                     ` Kaushik Barde
2007-02-12  7:43                       ` Keir Fraser [this message]
2007-02-06 15:43           ` Andrew D. Ball
2007-02-05  8:55         ` xensource (pci) device id's? Gerd Hoffmann
2007-02-01 20:02     ` Zulauf, John
2007-02-01 20:29       ` Ian Campbell
2007-02-01 23:22         ` Keir Fraser
2007-02-02  8:15         ` Gerd Hoffmann
2007-02-01 23:17       ` 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=C1F5CB2B.1863%Keir.Fraser@cl.cam.ac.uk \
    --to=keir.fraser@cl.cam.ac.uk \
    --cc=Kaushik_Barde@Phoenix.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.