lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 2 Sep 2014 10:28:00 +0200
From:	Alexander Spyridakis <>
To:	Marc Zyngier <>
Cc:	Hanjun Guo <>,
	"" <>,
	Catalin Marinas <>,
	Will Deacon <>,
	Lv Zheng <>, Rob Herring <>,
	Daniel Lezcano <>,
	Robert Moore <>,
	"" <>,
	Robert Richter <>,
	Jason Cooper <>,
	Arnd Bergmann <>,
	Liviu Dudau <>,
	Mark Brown <>,
	Bjorn Helgaas <>,
	Randy Dunlap <>,
	"Rafael J. Wysocki" <>,
	"" <>,
	Olof Johansson <>
Subject: Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific
 ACPI boot support

On 1 September 2014 19:35, Marc Zyngier <> wrote:
> On 01/09/14 15:57, Hanjun Guo wrote:
> > From: Tomasz Nowicki <>
> >
> > ACPI kernel uses MADT table for proper GIC initialization. It needs to
> > parse GIC related subtables, collect CPU interface and distributor
> > addresses and call driver initialization function (which is hardware
> > abstraction agnostic). In a similar way, FDT initialize GICv1/2.
> >
> > NOTE: This commit allow to initialize GICv1/2 only.
> I cannot help but notice that there is no support for KVM here. It'd be
> good to add a note to that effect, so that people do not expect
> virtualization support to be working when booting with ACPI.

Just a heads up for this, I run up to this problem too while testing
and by forcing some values for vgic and arch_timers I could boot a
QEMU guest without problems.

I'll try and see if it will be easy to handle this more properly
instead of hardcoded values.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists