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:	Sat, 20 Dec 2014 22:54:52 +0000
From:	Peter Maydell <>
To:	Arnd Bergmann <>
Cc:	arm-mail-list <>,
	Mark Rutland <>,
	"" <>,
	Jason Cooper <>,
	Pawel Moll <>,
	Ian Campbell <>,
	Marc Zyngier <>,
	Catalin Marinas <>,
	Mark Brown <>,
	Will Deacon <>,
	"" <>,
	Robert Richter <>,
	"" <>,
	Rob Herring <>,
	Matthias Brugger <>,
	Sascha Hauer <>,
	Kumar Gala <>,
	Olof Johansson <>,
	"Joe.C" <>,
	Thomas Gleixner <>,
	Eddie Huang <>
Subject: Re: [PATCH v2 3/4] arm64: dts: Add mediatek MT8173 SoC and evaluation
 board dts and Makefile

On 20 December 2014 at 20:07, Arnd Bergmann <> wrote:
> On Wednesday 17 December 2014 15:01:29 Marc Zyngier wrote:
>> Also it is worth noticing that given how GICV is placed, it will never
>> work with 64K pages and virtualization. Pretty sad.
> Does this mean no VGIC support on this platform so you have to emulate it
> in order to run virtual machines with 64K pages, or does it mean that
> it's impossible to use that way because you can't emulate it?

Currently having the guest use the generic timer requires an
in-kernel GIC, because we don't provide an ABI for having the
kernel say "here is a generic timer interrupt for the userspace
emulated GIC". And at least for QEMU userspace the "virt" board
doesn't provide any other kind of timer, so you'd need to add one
if you wanted to use a userspace GIC. So for practical purposes
"out-of-kernel GIC" is not a supported config for KVM+QEMU.

-- PMM
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