On Thu, 9 May 2019 at 15:27, Igor Mammedov wrote:
> It should be possible to add nvdimm and memory hotplug later.
> (I don't see big issues here, as long as it would be possible
> to carve out continuous range in address space for it.
>
> Considering ABI to guest, one could reuse QEMU's notificat
On Wed, 8 May 2019 19:22:53 +0800
Hongbo Zhang wrote:
> On Tue, 30 Apr 2019 at 22:04, Peter Maydell wrote:
> >
> > On Thu, 18 Apr 2019 at 05:05, Hongbo Zhang wrote:
> > >
> > > For the Aarch64, there is one machine 'virt', it is primarily meant to
> > > run on KVM and execute virtualization wor
On Tue, 30 Apr 2019 at 22:04, Peter Maydell wrote:
>
> On Thu, 18 Apr 2019 at 05:05, Hongbo Zhang wrote:
> >
> > For the Aarch64, there is one machine 'virt', it is primarily meant to
> > run on KVM and execute virtualization workloads, but we need an
> > environment as faithful as possible to ph
On Thu, 18 Apr 2019 at 05:05, Hongbo Zhang wrote:
>
> For the Aarch64, there is one machine 'virt', it is primarily meant to
> run on KVM and execute virtualization workloads, but we need an
> environment as faithful as possible to physical hardware, for supporting
> firmware and OS development fo
For the Aarch64, there is one machine 'virt', it is primarily meant to
run on KVM and execute virtualization workloads, but we need an
environment as faithful as possible to physical hardware, for supporting
firmware and OS development for pysical Aarch64 machines.
This patch introduces new machin
