On 10/01/15 14:22, Gabriel L. Somlo wrote:
> On Wed, Sep 30, 2015 at 12:21:08PM +0200, Laszlo Ersek wrote:
>> On 09/30/15 11:59, Ard Biesheuvel wrote:
>>> On 29 September 2015 at 20:26, Gabriel L. Somlo wrote:
On Tue, Sep 29, 2015 at 12:40:16PM +0200, Laszlo Ersek wrote:
> On 09/27/15 23:
On 1 October 2015 at 13:35, Laszlo Ersek wrote:
> On 10/01/15 14:22, Gabriel L. Somlo wrote:
>> I'm noticing that even on 32-bit arm there are ACPI tables generated and
>> inserted into fw_cfg, so is there any reason OTHER than lack of firmware
>> support for ACPI not being supported on 32-bit arm
On 1 October 2015 at 14:22, Gabriel L. Somlo wrote:
> On Wed, Sep 30, 2015 at 12:21:08PM +0200, Laszlo Ersek wrote:
>> On 09/30/15 11:59, Ard Biesheuvel wrote:
>> > On 29 September 2015 at 20:26, Gabriel L. Somlo wrote:
>> >> On Tue, Sep 29, 2015 at 12:40:16PM +0200, Laszlo Ersek wrote:
>> >>> On
On 10/01/15 14:39, Peter Maydell wrote:
> On 1 October 2015 at 13:35, Laszlo Ersek wrote:
>> On 10/01/15 14:22, Gabriel L. Somlo wrote:
>>> I'm noticing that even on 32-bit arm there are ACPI tables generated and
>>> inserted into fw_cfg, so is there any reason OTHER than lack of firmware
>>> supp
On Wed, Sep 30, 2015 at 12:21:08PM +0200, Laszlo Ersek wrote:
> On 09/30/15 11:59, Ard Biesheuvel wrote:
> > On 29 September 2015 at 20:26, Gabriel L. Somlo wrote:
> >> On Tue, Sep 29, 2015 at 12:40:16PM +0200, Laszlo Ersek wrote:
> >>> On 09/27/15 23:29, Gabriel L. Somlo wrote:
> Add a fw_cf
On Wed, Sep 30, 2015 at 02:22:26PM +0200, Laszlo Ersek wrote:
> On 09/30/15 13:13, Peter Maydell wrote:
> > On 30 September 2015 at 11:21, Laszlo Ersek wrote:
> >> However: if Gabriel has no access to actual aarch64 hardware (ie. cannot
> >> run KVM guests), then I don't think he should bother. Bo
Hi,
> Here's a timing from my new company laptop (Thinkpad W541, i7-4810MQ CPU
> @ 2.80GHz, running docked); QEMU built with --enable-debug:
Almost the same here.
> (2) From launching the EFI stub until the login prompt appears on the
> serial console: 3 minutes 46 seconds
Less than half that
On 30 September 2015 at 13:22, Laszlo Ersek wrote:
> (3) After logging in super fast, the time it takes to get a shell
> prompt: 50 seconds
That's bad. This should be more like 5 seconds at worst, it is for me.
This does depend a lot on how your guest is configured,
of course -- if you have a ful
On 09/30/15 13:13, Peter Maydell wrote:
> On 30 September 2015 at 11:21, Laszlo Ersek wrote:
>> However: if Gabriel has no access to actual aarch64 hardware (ie. cannot
>> run KVM guests), then I don't think he should bother. Booting just the
>> UEFI firmware on qemu-system-aarch64 with TCG accele
On 30 September 2015 at 11:21, Laszlo Ersek wrote:
> However: if Gabriel has no access to actual aarch64 hardware (ie. cannot
> run KVM guests), then I don't think he should bother. Booting just the
> UEFI firmware on qemu-system-aarch64 with TCG acceleration is fine, but
> for checking "/proc/iom
test results from an aarch64 Linux guest (using KVM and UEFI):
On 09/29/15 12:40, Laszlo Ersek wrote:
> On 09/27/15 23:29, Gabriel L. Somlo wrote:
>> Add a fw_cfg device node to the ACPI DSDT. This is mostly
>> informational, as the authoritative fw_cfg MMIO region(s)
>> are listed in the Device T
On 09/30/15 11:59, Ard Biesheuvel wrote:
> On 29 September 2015 at 20:26, Gabriel L. Somlo wrote:
>> On Tue, Sep 29, 2015 at 12:40:16PM +0200, Laszlo Ersek wrote:
>>> On 09/27/15 23:29, Gabriel L. Somlo wrote:
Add a fw_cfg device node to the ACPI DSDT. This is mostly
informational, as th
On 29 September 2015 at 20:26, Gabriel L. Somlo wrote:
> On Tue, Sep 29, 2015 at 12:40:16PM +0200, Laszlo Ersek wrote:
>> On 09/27/15 23:29, Gabriel L. Somlo wrote:
>> > Add a fw_cfg device node to the ACPI DSDT. This is mostly
>> > informational, as the authoritative fw_cfg MMIO region(s)
>> > ar
On Tue, Sep 29, 2015 at 12:40:16PM +0200, Laszlo Ersek wrote:
> On 09/27/15 23:29, Gabriel L. Somlo wrote:
> > Add a fw_cfg device node to the ACPI DSDT. This is mostly
> > informational, as the authoritative fw_cfg MMIO region(s)
> > are listed in the Device Tree. However, since we are building
>
On 09/29/15 20:26, Gabriel L. Somlo wrote:
> On Tue, Sep 29, 2015 at 12:40:16PM +0200, Laszlo Ersek wrote:
>> On 09/27/15 23:29, Gabriel L. Somlo wrote:
>>> Add a fw_cfg device node to the ACPI DSDT. This is mostly
>>> informational, as the authoritative fw_cfg MMIO region(s)
>>> are listed in the
On 09/27/15 23:29, Gabriel L. Somlo wrote:
> Add a fw_cfg device node to the ACPI DSDT. This is mostly
> informational, as the authoritative fw_cfg MMIO region(s)
> are listed in the Device Tree. However, since we are building
> ACPI tables, we might as well be thorough while at it...
>
> Signed-o
Add a fw_cfg device node to the ACPI DSDT. This is mostly
informational, as the authoritative fw_cfg MMIO region(s)
are listed in the Device Tree. However, since we are building
ACPI tables, we might as well be thorough while at it...
Signed-off-by: Gabriel Somlo
---
hw/arm/virt-acpi-build.c | 1
17 matches
Mail list logo
