[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] HVMlite ABI specification DRAFT A
- To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, Roger Pau Monnà <roger.pau@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, David Vrabel <david.vrabel@xxxxxxxxxx>, Paul Durrant <paul.durrant@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>
- From: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
- Date: Thu, 4 Feb 2016 14:18:46 -0500
- Delivery-date: Thu, 04 Feb 2016 19:19:13 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 02/04/2016 02:09 PM, Samuel Thibault wrote:
Roger Pau Monné, on Thu 04 Feb 2016 18:48:14 +0100, wrote:
struct hvm_start_info {
#define HVM_START_MAGIC_VALUE 0x336ec578
uint32_t magic; /* Contains the magic value 0x336ec578
*/
/* ("xEn3" with the 0x80 bit of the "E"
set).*/
uint32_t flags; /* SIF_xxx flags.
*/
uint32_t cmdline_paddr; /* Physical address of the command line.
*/
uint32_t nr_modules; /* Number of modules passed to the kernel.
*/
uint32_t modlist_paddr; /* Physical address of an array of
*/
/* hvm_modlist_entry.
*/
};
Mmm, don't we also need a description of the initial page table, so that
the guest kernel knows which part of the memory it shouldn't use until
having initialized its own page table? Or is there none in the guest
physical memory at startup of HVMlite mode?
We start with paging off. CR0 only has PE bit set when guest is loaded.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
