Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-14 Thread Radoslaw Biernacki
If running full machine stack is an option, than I think that you will be able to use SBSA machine in your tests once we have all the FW images ready. But unfortunately we are not there yet. niedz., 14 lip 2019, 23:57 użytkownik Guenter Roeck napisał: > On 7/14/19 8:40 AM, Radoslaw Biernacki

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-14 Thread Guenter Roeck
On 7/14/19 8:40 AM, Radoslaw Biernacki wrote: This machine is not ment for direct kernel boot. Is main purpose is development of FW, kernel and other HW/SW parts for SBSA. We are currently working on UEFI and ATF for this machine. It might be somehow possible to run kernel with DT but we do

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-14 Thread Radoslaw Biernacki
This machine is not ment for direct kernel boot. Is main purpose is development of FW, kernel and other HW/SW parts for SBSA. We are currently working on UEFI and ATF for this machine. It might be somehow possible to run kernel with DT but we do not support it at this moment. If all you want is

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-14 Thread Guenter Roeck
Hi, On Sun, Jun 30, 2019 at 06:20:32PM +0800, 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

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-01 Thread Hongbo Zhang
On Mon, 1 Jul 2019 at 22:54, Peter Maydell wrote: > > On Sun, 30 Jun 2019 at 11:21, 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

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-01 Thread Hongbo Zhang
On Tue, 2 Jul 2019 at 00:08, Leif Lindholm wrote: > > Hi Peter, > > On Mon, Jul 01, 2019 at 03:54:24PM +0100, Peter Maydell wrote: > > I've pointed out a number of issues with these patches, but they > > all turn out to be very minor (mostly fixable by moving code between > > patch 1 and 2). The

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-01 Thread Leif Lindholm
Hi Peter, On Mon, Jul 01, 2019 at 03:54:24PM +0100, Peter Maydell wrote: > I've pointed out a number of issues with these patches, but they > all turn out to be very minor (mostly fixable by moving code between > patch 1 and 2). The other thing we need is a MAINTAINERS section for > the new

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-01 Thread Radoslaw Biernacki
Hi Leif and Peter, We talked with Hongbo about the takeover, so please add me as maintainer. On Mon, 1 Jul 2019 at 18:08, Leif Lindholm wrote: > Hi Peter, > > On Mon, Jul 01, 2019 at 03:54:24PM +0100, Peter Maydell wrote: > > I've pointed out a number of issues with these patches, but they >

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-01 Thread Peter Maydell
On Mon, 1 Jul 2019 at 17:23, Radoslaw Biernacki wrote: > > Hi Leif and Peter, > > We talked with Hongbo about the takeover, so please add me as maintainer. Thanks for volunteering; I've updated the MAINTAINERS entry in my target-arm queue as Leif suggests. thanks -- PMM

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-01 Thread Peter Maydell
On Sun, 30 Jun 2019 at 11:21, 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

Re: [Qemu-devel] [PATCH v9 0/2] Add Arm SBSA Reference Machine

2019-07-01 Thread Peter Maydell
On Sun, 30 Jun 2019 at 11:21, 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