On Wed, 2015-09-02 at 12:39 +0100, Julien Grall wrote:
> Hi Ian,
>
> On 02/09/15 12:30, Ian Campbell wrote:
> > > Although, when running on Xen, FreeBSD is creating a Xen console by
> > > default with the higher priority. It will be grabbed by FreeBSD as
> > > the
> > > default one.
> >
> > ...
Hi Ian,
On 02/09/15 12:30, Ian Campbell wrote:
>> Although, when running on Xen, FreeBSD is creating a Xen console by
>> default with the higher priority. It will be grabbed by FreeBSD as the
>> default one.
>
> ... Linux should be doing the same. The problem is that the existing code
> to call a
On Wed, 2015-08-12 at 13:20 +0100, Julien Grall wrote:
> On 12/08/15 11:36, Andrew Turner wrote:
> > Would it be possible to add a stdout property and node for the hvc0
> > device? It would help FreeBSD as we use this to find the kernel
> > console. We check for the stdout-path, linux,stdout-path,
On Wed, 2015-08-12 at 13:11 +0100, Julien Grall wrote:
> On 12/08/15 12:23, Ian Campbell wrote:
> > Strictly it is considered a separate thing, much like loader.efi, despite
> > where it lives e.g. it is self contained and not allowed to call into the
> > kernel proper except via the formal interfa
On 2015/8/17 18:36, Roger Pau Monné wrote:
> El 11/08/15 a les 16.19, Ian Campbell ha escrit:
>> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
>>> This document is going to explain the design details of Xen booting with
>>> ACPI on ARM. Maybe parts of it may not be appropriate. Any comme
El 11/08/15 a les 16.19, Ian Campbell ha escrit:
> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
>> This document is going to explain the design details of Xen booting with
>> ACPI on ARM. Maybe parts of it may not be appropriate. Any comments are
>> welcome.
>
> Some small subsets of thi
On 2015/8/12 17:11, Julien Grall wrote:
On 12/08/2015 08:22, Shannon Zhao wrote:
Hi,
Hi Shannon,
It's not part of the design discussion and we are avoiding to mix
discussion. Can you please create another thread (or at least renaming
the subject)?
I'm working on re-spinning this patchset
On Fri, 14 Aug 2015, Shannon Zhao wrote:
> On 2015/8/13 18:29, Christoffer Dall wrote:
> > On Thu, Aug 13, 2015 at 11:22:19AM +0100, Ian Campbell wrote:
> >> > On Thu, 2015-08-13 at 11:13 +0100, Stefano Stabellini wrote:
> >>> > >
> > > > > > For example it is only natural for the kernel to tr
On 2015/8/13 18:29, Christoffer Dall wrote:
> On Thu, Aug 13, 2015 at 11:22:19AM +0100, Ian Campbell wrote:
>> > On Thu, 2015-08-13 at 11:13 +0100, Stefano Stabellini wrote:
>>> > >
> > > > > For example it is only natural for the kernel to try to use the
> > > > > GIC
> > > > > hy
On Thu, 2015-08-13 at 13:08 +0100, Julien Grall wrote:
>
> The MADT has to be modified in order to let DOM0 knows about his CPU
> topology. If ever need the original MADT for power management, then we
> should find a Xen specific way to do it (even if it's passing the
> orginal MADT as a backup).
On 13/08/15 12:55, Jan Beulich wrote:
On 13.08.15 at 13:00, wrote:
>> On 13/08/15 11:54, Jan Beulich wrote:
>> On 13.08.15 at 12:48, wrote:
On 2015/8/13 18:29, Christoffer Dall wrote:
> However, what about for other resources? Having code somewhere that
> says "hide this ra
>>> On 13.08.15 at 13:00, wrote:
> On 13/08/15 11:54, Jan Beulich wrote:
> On 13.08.15 at 12:48, wrote:
>>> On 2015/8/13 18:29, Christoffer Dall wrote:
However, what about for other resources? Having code somewhere that
says "hide this random piece of hardware if you're Xen dom0" s
On Thu, 13 Aug 2015, Julien Grall wrote:
> On 13/08/15 11:54, Jan Beulich wrote:
> On 13.08.15 at 12:48, wrote:
> >> On 2015/8/13 18:29, Christoffer Dall wrote:
> >>> However, what about for other resources? Having code somewhere that
> >>> says "hide this random piece of hardware if you're
On 13/08/15 11:54, Jan Beulich wrote:
On 13.08.15 at 12:48, wrote:
>> On 2015/8/13 18:29, Christoffer Dall wrote:
>>> However, what about for other resources? Having code somewhere that
>>> says "hide this random piece of hardware if you're Xen dom0" sounds
>>> awful to me. I know it's only
>>> On 13.08.15 at 12:48, wrote:
> On 2015/8/13 18:29, Christoffer Dall wrote:
>> However, what about for other resources? Having code somewhere that
>> says "hide this random piece of hardware if you're Xen dom0" sounds
>> awful to me. I know it's only the serial port right now, but still.
>>
On 2015/8/13 18:29, Christoffer Dall wrote:
> On Thu, Aug 13, 2015 at 11:22:19AM +0100, Ian Campbell wrote:
>> On Thu, 2015-08-13 at 11:13 +0100, Stefano Stabellini wrote:
>>>
> For example it is only natural for the kernel to try to use the GIC
> hyp
> functionalities if they are de
On 13/08/15 10:20, Jan Beulich wrote:
>> BTW, IIRC x86 does modify at least one ACPI table which is the DMAR (I
>> think), to hide the IOMMU from the guest? That's another table we would
>> want to frob on ARM I think (or it's equivalent, which I think is IORT).
>
> Eliminating that hack is suppos
On Thu, 2015-08-13 at 12:29 +0200, Christoffer Dall wrote:
> On Thu, Aug 13, 2015 at 11:22:19AM +0100, Ian Campbell wrote:
> > On Thu, 2015-08-13 at 11:13 +0100, Stefano Stabellini wrote:
> > >
> > > > > For example it is only natural for the kernel to try to use the
> > > > > GIC
> > > > > hyp
On Thu, 13 Aug 2015, Christoffer Dall wrote:
> On Thu, Aug 13, 2015 at 11:22:19AM +0100, Ian Campbell wrote:
> > On Thu, 2015-08-13 at 11:13 +0100, Stefano Stabellini wrote:
> > >
> > > > > For example it is only natural for the kernel to try to use the GIC
> > > > > hyp
> > > > > functionalities
On Thu, Aug 13, 2015 at 11:22:19AM +0100, Ian Campbell wrote:
> On Thu, 2015-08-13 at 11:13 +0100, Stefano Stabellini wrote:
> >
> > > > For example it is only natural for the kernel to try to use the GIC
> > > > hyp
> > > > functionalities if they are described, while actually they are not
> > >
On Thu, 2015-08-13 at 11:13 +0100, Stefano Stabellini wrote:
>
> > > For example it is only natural for the kernel to try to use the GIC
> > > hyp
> > > functionalities if they are described, while actually they are not
> > > emulated by Xen at all.
> >
> > See Ian's earlier reply: It can also b
On Thu, 13 Aug 2015, Jan Beulich wrote:
> >>> On 13.08.15 at 11:43, wrote:
> > On Thu, 13 Aug 2015, Jan Beulich wrote:
> >> >>> On 12.08.15 at 18:18, wrote:
> >> > On 12/08/15 16:58, Jan Beulich wrote:
> >> > On 12.08.15 at 17:51, wrote:
> >> >>> On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich
>>> On 13.08.15 at 11:43, wrote:
> On Thu, 13 Aug 2015, Jan Beulich wrote:
>> >>> On 12.08.15 at 18:18, wrote:
>> > On 12/08/15 16:58, Jan Beulich wrote:
>> > On 12.08.15 at 17:51, wrote:
>> >>> On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich wrote:
>> >>> On 07.08.15 at 04:11, wrote:
>>
On Thu, 13 Aug 2015, Jan Beulich wrote:
> >>> On 12.08.15 at 18:18, wrote:
> > On 12/08/15 16:58, Jan Beulich wrote:
> > On 12.08.15 at 17:51, wrote:
> >>> On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich wrote:
> >>> On 07.08.15 at 04:11, wrote:
> > All these tables will be copied to D
>>> On 13.08.15 at 11:05, wrote:
> The other reason for modification is to hide the Xen console device (i.e.
> one UART) from the dom0 kernel, since it is unusable. How does that work on
> x86? Do you just not bother and you expect the admin to arrange the
> configuration to work or is there some
On Thu, 2015-08-13 at 00:41 -0600, Jan Beulich wrote:
> >
> > Nonetheless, we still have to copy some table in Xen in order to modify
> > them and/or new one. I have in mind the FADT table to set the hypervisor
> > field and hiding the hypervisor specific data (GIC hyp, timer hyp...) to
> > avoid
>>> On 13.08.15 at 10:01, wrote:
> On Thu, Aug 13, 2015 at 8:41 AM, Jan Beulich wrote:
> On 12.08.15 at 18:18, wrote:
>>> Nonetheless, we still have to copy some table in Xen in order to modify
>>> them and/or new one. I have in mind the FADT table to set the hypervisor
>>> field and hiding
>>> On 13.08.15 at 10:01, wrote:
> On Thu, Aug 13, 2015 at 8:41 AM, Jan Beulich wrote:
> On 12.08.15 at 18:18, wrote:
>>> Nonetheless, we still have to copy some table in Xen in order to modify
>>> them and/or new one. I have in mind the FADT table to set the hypervisor
>>> field and hiding
On Thu, Aug 13, 2015 at 8:41 AM, Jan Beulich wrote:
On 12.08.15 at 18:18, wrote:
>> On 12/08/15 16:58, Jan Beulich wrote:
>> On 12.08.15 at 17:51, wrote:
On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich wrote:
On 07.08.15 at 04:11, wrote:
>> All these tables will be copi
>>> On 12.08.15 at 18:18, wrote:
> On 12/08/15 16:58, Jan Beulich wrote:
> On 12.08.15 at 17:51, wrote:
>>> On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich wrote:
>>> On 07.08.15 at 04:11, wrote:
> All these tables will be copied to Dom0 memory except that the reused
> tables(DSDT,
On 12/08/15 16:58, Jan Beulich wrote:
On 12.08.15 at 17:51, wrote:
>> On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich wrote:
>> On 07.08.15 at 04:11, wrote:
All these tables will be copied to Dom0 memory except that the reused
tables(DSDT, SPCR, etc) will be mapped to Dom0.
>>>
>
On Wed, 12 Aug 2015 10:21:55 +0100
Julien Grall wrote:
> Hi,
>
> (Cc Andrew Turner who worked on the ACPI port for FreeBSD ARM64)
>
> On 12/08/2015 09:52, Ian Campbell wrote:
> > On Wed, 2015-08-12 at 11:04 +0800, Shannon Zhao wrote:
> >> Hi Julien,
> >>
> >> On 2015/8/12 0:19, Julien Grall wro
>>> On 12.08.15 at 17:51, wrote:
> On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich wrote:
> On 07.08.15 at 04:11, wrote:
>>> All these tables will be copied to Dom0 memory except that the reused
>>> tables(DSDT, SPCR, etc) will be mapped to Dom0.
>>
>> Which again seems odd - such tables should
On Wed, Aug 12, 2015 at 5:45 PM, Jan Beulich wrote:
On 07.08.15 at 04:11, wrote:
>> 1. Copy and change some EFI and ACPI tables
>> ---
>
> A key thing I'm missing here is reasoning of why this copying approach
> is needed in the first place. Remember t
>>> On 11.08.15 at 16:12, wrote:
> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
>>
> [...]
>> 3. Dom0 gets grant table and event channel irq information
>> ---
>> As said above, we assign the hypervisor_id be "XenVMM" to tell Dom0
>>> On 07.08.15 at 04:11, wrote:
> 1. Copy and change some EFI and ACPI tables
> ---
A key thing I'm missing here is reasoning of why this copying approach
is needed in the first place. Remember that on the x86 side we get
away without any such copying-and-
On 12/08/15 11:36, Andrew Turner wrote:
> Would it be possible to add a stdout property and node for the hvc0
> device? It would help FreeBSD as we use this to find the kernel
> console. We check for the stdout-path, linux,stdout-path, stdout,
> stdin-path, and stdin properties, in that order, with
On 12/08/15 12:23, Ian Campbell wrote:
> Strictly it is considered a separate thing, much like loader.efi, despite
> where it lives e.g. it is self contained and not allowed to call into the
> kernel proper except via the formal interface provided for the hand-off.
>
> That might seem like semanti
On Wed, 2015-08-12 at 11:48 +0100, Stefano Stabellini wrote:
> On Wed, 12 Aug 2015, Andrew Turner wrote:
> > On Wed, 12 Aug 2015 10:21:55 +0100
> > Julien Grall wrote:
> >
> > > Hi,
> > >
> > > (Cc Andrew Turner who worked on the ACPI port for FreeBSD ARM64)
> > >
> > > On 12/08/2015 09:52, Ian
On Wed, 12 Aug 2015, Andrew Turner wrote:
> On Wed, 12 Aug 2015 10:21:55 +0100
> Julien Grall wrote:
>
> > Hi,
> >
> > (Cc Andrew Turner who worked on the ACPI port for FreeBSD ARM64)
> >
> > On 12/08/2015 09:52, Ian Campbell wrote:
> > > On Wed, 2015-08-12 at 11:04 +0800, Shannon Zhao wrote:
>
On Wed, 12 Aug 2015, Ian Campbell wrote:
> On Wed, 2015-08-12 at 11:04 +0800, Shannon Zhao wrote:
> > Hi Julien,
> >
> > On 2015/8/12 0:19, Julien Grall wrote:
> > > Hi Shannon,
> > >
> > > On 07/08/15 03:11, Shannon Zhao wrote:
> > > > 2. Create minimal DT to pass required information to Dom0
>
Hi,
(Cc Andrew Turner who worked on the ACPI port for FreeBSD ARM64)
On 12/08/2015 09:52, Ian Campbell wrote:
On Wed, 2015-08-12 at 11:04 +0800, Shannon Zhao wrote:
Hi Julien,
On 2015/8/12 0:19, Julien Grall wrote:
Hi Shannon,
On 07/08/15 03:11, Shannon Zhao wrote:
2. Create minimal DT to
On 12/08/2015 08:22, Shannon Zhao wrote:
Hi,
Hi Shannon,
It's not part of the design discussion and we are avoiding to mix
discussion. Can you please create another thread (or at least renaming
the subject)?
I'm working on re-spinning this patchset while encountering a werid
problem about
On 12/08/2015 09:46, Ian Campbell wrote:
On Tue, 2015-08-11 at 17:01 +0100, Julien Grall wrote:
On 11/08/15 16:19, Ian Campbell wrote:
IIRC we talked about it few months ago and you said that using
balloon
page will split in 4K the 1G/2M mapping done in the stage-2 p2m.
Did I? Odd because I
On 2015/8/12 16:47, Ian Campbell wrote:
> On Wed, 2015-08-12 at 10:47 +0800, Shannon Zhao wrote:
>>
>> On 2015/8/11 23:52, Boris Ostrovsky wrote:
>>> On 08/11/2015 11:35 AM, Ian Campbell wrote:
On Tue, 2015-08-11 at 11:29 -0400, Boris Ostrovsky wrote:
> On 08/11/2015 10:21 AM, Ian Campbe
On Wed, 2015-08-12 at 11:04 +0800, Shannon Zhao wrote:
> Hi Julien,
>
> On 2015/8/12 0:19, Julien Grall wrote:
> > Hi Shannon,
> >
> > On 07/08/15 03:11, Shannon Zhao wrote:
> > > 2. Create minimal DT to pass required information to Dom0
> > > -
On Wed, 2015-08-12 at 10:47 +0800, Shannon Zhao wrote:
>
> On 2015/8/11 23:52, Boris Ostrovsky wrote:
> > On 08/11/2015 11:35 AM, Ian Campbell wrote:
> > > On Tue, 2015-08-11 at 11:29 -0400, Boris Ostrovsky wrote:
> > > > On 08/11/2015 10:21 AM, Ian Campbell wrote:
> > > > > On Tue, 2015-08-11 at
On Wed, 2015-08-12 at 10:42 +0800, Shannon Zhao wrote:
>
> On 2015/8/12 0:01, Julien Grall wrote:
> > On 11/08/15 16:19, Ian Campbell wrote:
> > > > IIRC we talked about it few months ago and you said that using
> > > > balloon
> > > > page will split in 4K the 1G/2M mapping done in the stage-2 p
On Tue, 2015-08-11 at 17:01 +0100, Julien Grall wrote:
> On 11/08/15 16:19, Ian Campbell wrote:
> > > IIRC we talked about it few months ago and you said that using
> > > balloon
> > > page will split in 4K the 1G/2M mapping done in the stage-2 p2m.
> >
> > Did I? Odd because I'm also of the opin
Hi,
I'm working on re-spinning this patchset while encountering a werid
problem about xzalloc_bytes.
Since I need to copy some ACPI tables, I need to allocate some memory
for it. So there are a few places calling xzalloc_bytes. And it fails at
the fifth one. The log is shown as following:
(XEN)
Hi Julien,
On 2015/8/12 0:19, Julien Grall wrote:
> Hi Shannon,
>
> On 07/08/15 03:11, Shannon Zhao wrote:
>> 2. Create minimal DT to pass required information to Dom0
>> --
>> The minimal DT mainly passes Dom0 bootargs, address and size of
On 2015/8/11 23:52, Boris Ostrovsky wrote:
> On 08/11/2015 11:35 AM, Ian Campbell wrote:
>> On Tue, 2015-08-11 at 11:29 -0400, Boris Ostrovsky wrote:
>>> On 08/11/2015 10:21 AM, Ian Campbell wrote:
On Tue, 2015-08-11 at 15:19 +0100, Ian Campbell wrote:
> On Fri, 2015-08-07 at 10:11 +0800
On 2015/8/12 0:01, Julien Grall wrote:
> On 11/08/15 16:19, Ian Campbell wrote:
>>> IIRC we talked about it few months ago and you said that using balloon
>>> page will split in 4K the 1G/2M mapping done in the stage-2 p2m.
>>
>> Did I? Odd because I'm also of the opinion that alloc_ballooned_pag
Hi Shannon,
On 07/08/15 03:11, Shannon Zhao wrote:
> 2. Create minimal DT to pass required information to Dom0
> --
> The minimal DT mainly passes Dom0 bootargs, address and size of initrd
> (if available), address and size of uefi system tab
On 11/08/15 16:19, Ian Campbell wrote:
>> IIRC we talked about it few months ago and you said that using balloon
>> page will split in 4K the 1G/2M mapping done in the stage-2 p2m.
>
> Did I? Odd because I'm also of the opinion that alloc_ballooned_pages
> should operate in chunks of 2M at the hyp
On 08/11/2015 11:35 AM, Ian Campbell wrote:
On Tue, 2015-08-11 at 11:29 -0400, Boris Ostrovsky wrote:
On 08/11/2015 10:21 AM, Ian Campbell wrote:
On Tue, 2015-08-11 at 15:19 +0100, Ian Campbell wrote:
On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
This document is going to explain the
On Tue, 2015-08-11 at 11:29 -0400, Boris Ostrovsky wrote:
> On 08/11/2015 10:21 AM, Ian Campbell wrote:
> > On Tue, 2015-08-11 at 15:19 +0100, Ian Campbell wrote:
> > > On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
> > > > This document is going to explain the design details of Xen booting
On 08/11/2015 10:21 AM, Ian Campbell wrote:
On Tue, 2015-08-11 at 15:19 +0100, Ian Campbell wrote:
On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
This document is going to explain the design details of Xen booting
with
ACPI on ARM. Maybe parts of it may not be appropriate. Any comments
On 11/08/15 16:19, Ian Campbell wrote:
> On Tue, 2015-08-11 at 16:11 +0100, Julien Grall wrote:
>> On 11/08/15 15:59, Ian Campbell wrote:
>>> On Tue, 2015-08-11 at 15:51 +0100, David Vrabel wrote:
On 11/08/15 15:12, Ian Campbell wrote:
> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrot
On Tue, 2015-08-11 at 16:11 +0100, Julien Grall wrote:
> On 11/08/15 15:59, Ian Campbell wrote:
> > On Tue, 2015-08-11 at 15:51 +0100, David Vrabel wrote:
> > > On 11/08/15 15:12, Ian Campbell wrote:
> > > > On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
> > > > >
> > > > [...]
> > > > > 3
On 11/08/15 15:59, Ian Campbell wrote:
> On Tue, 2015-08-11 at 15:51 +0100, David Vrabel wrote:
>> On 11/08/15 15:12, Ian Campbell wrote:
>>> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
>>> [...]
3. Dom0 gets grant table and event channel irq information
--
On 11/08/15 15:59, Ian Campbell wrote:
> On Tue, 2015-08-11 at 15:51 +0100, David Vrabel wrote:
>> On 11/08/15 15:12, Ian Campbell wrote:
>>> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
>>> [...]
3. Dom0 gets grant table and event channel irq information
--
On Tue, 2015-08-11 at 15:51 +0100, David Vrabel wrote:
> On 11/08/15 15:12, Ian Campbell wrote:
> > On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
> > >
> > [...]
> > > 3. Dom0 gets grant table and event channel irq information
> > >
On 11/08/15 15:12, Ian Campbell wrote:
> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
>>
> [...]
>> 3. Dom0 gets grant table and event channel irq information
>> ---
>> As said above, we assign the hypervisor_id be "XenVMM" to tell D
On Tue, 2015-08-11 at 15:19 +0100, Ian Campbell wrote:
> On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
> > This document is going to explain the design details of Xen booting
> > with
> > ACPI on ARM. Maybe parts of it may not be appropriate. Any comments are
> > welcome.
>
> Some small
On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
> This document is going to explain the design details of Xen booting with
> ACPI on ARM. Maybe parts of it may not be appropriate. Any comments are
> welcome.
Some small subsets of this seem like they might overlap with what will be
required
On Fri, 2015-08-07 at 10:11 +0800, Shannon Zhao wrote:
>
[...]
> 3. Dom0 gets grant table and event channel irq information
> ---
> As said above, we assign the hypervisor_id be "XenVMM" to tell Dom0 that
> it runs on Xen hypervisor.
>
> For
On 2015/8/11 17:46, Julien Grall wrote:
> On 11/08/15 03:09, Shannon Zhao wrote:
>> Hi Julien,
>
> Hi Shannon,
>
>> On 2015/8/7 18:33, Julien Grall wrote:
>>> Hi Shannon,
>>>
>>> Just some clarification questions.
>>>
>>> On 07/08/15 03:11, Shannon Zhao wrote:
3. Dom0 gets grant table and
On 11/08/15 03:09, Shannon Zhao wrote:
> Hi Julien,
Hi Shannon,
> On 2015/8/7 18:33, Julien Grall wrote:
>> Hi Shannon,
>>
>> Just some clarification questions.
>>
>> On 07/08/15 03:11, Shannon Zhao wrote:
>>> 3. Dom0 gets grant table and event channel irq information
>>>
Hi Julien,
On 2015/8/7 18:33, Julien Grall wrote:
> Hi Shannon,
>
> Just some clarification questions.
>
> On 07/08/15 03:11, Shannon Zhao wrote:
>> 3. Dom0 gets grant table and event channel irq information
>> ---
>> As said above, we assi
On 07/08/15 11:37, Christoffer Dall wrote:
> On Fri, Aug 7, 2015 at 12:33 PM, Julien Grall wrote:
>> Hi Shannon,
>>
>> Just some clarification questions.
>>
>> On 07/08/15 03:11, Shannon Zhao wrote:
>>> 3. Dom0 gets grant table and event channel irq information
>>>
On Fri, 7 Aug 2015, Christoffer Dall wrote:
> On Fri, Aug 7, 2015 at 12:33 PM, Julien Grall wrote:
> > Hi Shannon,
> >
> > Just some clarification questions.
> >
> > On 07/08/15 03:11, Shannon Zhao wrote:
> >> 3. Dom0 gets grant table and event channel irq information
> >>
On Fri, Aug 7, 2015 at 12:33 PM, Julien Grall wrote:
> Hi Shannon,
>
> Just some clarification questions.
>
> On 07/08/15 03:11, Shannon Zhao wrote:
>> 3. Dom0 gets grant table and event channel irq information
>> ---
>> As said above, we ass
Hi Shannon,
Just some clarification questions.
On 07/08/15 03:11, Shannon Zhao wrote:
> 3. Dom0 gets grant table and event channel irq information
> ---
> As said above, we assign the hypervisor_id be "XenVMM" to tell Dom0 that
> it runs on
On Fri, 7 Aug 2015, Shannon Zhao wrote:
> This document is going to explain the design details of Xen booting with
> ACPI on ARM. Maybe parts of it may not be appropriate. Any comments are
> welcome.
>
> To Xen itself booting with ACPI, this is similar to Linux kernel except
> that Xen doesn't par
This document is going to explain the design details of Xen booting with
ACPI on ARM. Maybe parts of it may not be appropriate. Any comments are
welcome.
To Xen itself booting with ACPI, this is similar to Linux kernel except
that Xen doesn't parse DSDT table. So I'll skip this part and focus on
h
76 matches
Mail list logo
