On Fri, 16 Nov 2018 at 17:58, Peter Maydell wrote:
>
> On 16 November 2018 at 08:23, Hongbo Zhang wrote:
> > Well, for the SMP booting, when GICv2 used, there is no problem, max
> > CPU number 8 can be booted, including all the three cases: kernel
> > only, UEFI+kernel and ATF+UEFI+kernel.
> >
>
On 16 November 2018 at 08:23, Hongbo Zhang wrote:
> Well, for the SMP booting, when GICv2 used, there is no problem, max
> CPU number 8 can be booted, including all the three cases: kernel
> only, UEFI+kernel and ATF+UEFI+kernel.
>
> But when GICv3 used, these two cases still work: kernel only,
On Fri, 16 Nov 2018 at 00:21, Peter Maydell wrote:
>
> On 19 October 2018 at 09:55, Hongbo Zhang wrote:
> > there are two commit reverts I have to do to boot system currently, these
> > block not only my new 'sbsa-ref', but also the 'virt'.
> > (other two workarounds can be ignored, they are
On Thu, 15 Nov 2018 at 08:21, Peter Maydell wrote:
>
> On 19 October 2018 at 09:55, Hongbo Zhang wrote:
> > there are two commit reverts I have to do to boot system currently, these
> > block not only my new 'sbsa-ref', but also the 'virt'.
> > (other two workarounds can be ignored, they are
On 19 October 2018 at 09:55, Hongbo Zhang wrote:
> there are two commit reverts I have to do to boot system currently, these
> block not only my new 'sbsa-ref', but also the 'virt'.
> (other two workarounds can be ignored, they are just for temp using before
> firmware porting is fully
On 6 November 2018 at 00:31, Peter Maydell wrote:
> On 19 October 2018 at 09:55, 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
On 19 October 2018 at 09:55, 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, to support
> firmware and OS development for
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, to support
firmware and OS development for pysical Aarch64 machines.
See the patch commit comments for
