On 23/11/2017 10:54, Cornelia Huck wrote:
On Wed, 22 Nov 2017 23:05:29 +0100
Pierre Morel wrote:
Enhance the fault detection, correction of the fault reporting.
Signed-off-by: Pierre Morel
Reviewed-by: Yi Min Zhao
---
hw/s390x/s390-pci-inst.c | 39 ++-
On 23/11/2017 10:01, Thomas Huth wrote:
On 22.11.2017 23:05, Pierre Morel wrote:
Enhance the fault detection, correction of the fault reporting.
Signed-off-by: Pierre Morel
Reviewed-by: Yi Min Zhao
---
hw/s390x/s390-pci-inst.c | 39 ++-
1 file changed, 2
On 23/11/2017 10:32, Thomas Huth wrote:
On 22.11.2017 23:05, Pierre Morel wrote:
Let's move the memory region read from pcilg into a dedicated function.
This allows us to prepare a later patch.
Signed-off-by: Pierre Morel
Reviewed-by: Yi Min Zhao
---
hw/s390x/s390-pci-inst.c | 15 ++
On 23/11/2017 10:36, Thomas Huth wrote:
On 22.11.2017 23:05, Pierre Morel wrote:
Let's move the memory region write from pcistg into a dedicated
function.
This allows us to prepare a later patch searching for subregions
inside of the memory region.
Signed-off-by: Pierre Morel
Reviewed-by: Yi M
On 24/11/2017 07:19, Yi Min Zhao wrote:
在 2017/11/23 下午8:18, Thomas Huth 写道:
On 23.11.2017 13:07, Yi Min Zhao wrote:
在 2017/11/23 下午6:33, Cornelia Huck 写道:
On Thu, 23 Nov 2017 11:25:10 +0100
Thomas Huth wrote:
On 23.11.2017 11:08, Cornelia Huck wrote:
On Thu, 23 Nov 2017 11:01:23 +0100
Changes v1 (RFC) -> v2:
* Patch 1 now just adds TYPE_SYS_BUS_DEVICE to the existing
has_dynamic_sysbus=true machines, and other patches make
the lists on each machine-type more specific.
* Change the name of the new field to
allowed_dynamic_sysbus_devices.
* The q35 allowed list is much short
Replace the TYPE_SYS_BUS_DEVICE entry in the allowed sysbus
device list with the two device types that are really supported
by the virt machine: vfio-amd-xgbe and vfio-calxeda-xgmac.
Cc: Peter Maydell
Cc: qemu-...@nongnu.org
Signed-off-by: Eduardo Habkost
---
Changes series v1 -> v2:
* New patch
The existing has_dynamic_sysbus flag makes the machine accept
every user-creatable sysbus device type on the command-line.
Replace it with a list of allowed device types, so machines can
easily accept some sysbus devices while rejecting others.
To keep exactly the same behavior as before, the exis
platform_bus_create_devtree() already rejects all dynamic sysbus
devices except TYPE_ETSEC_COMMON, so register it as the only
allowed dynamic sysbus device for the ppce500 machine-type.
Cc: Alexander Graf
Cc: David Gibson
Cc: qemu-...@nongnu.org
Signed-off-by: Eduardo Habkost
---
Changes series
TYPE_SPAPR_PCI_HOST_BRIDGE is the only dynamic sysbus device not
rejected by ppc_spapr_reset(), so it can be the only entry on the
allowed list.
Cc: David Gibson
Cc: Alexander Graf
Cc: qemu-...@nongnu.org
Signed-off-by: Eduardo Habkost
---
Changes series v1 -> v2:
* New patch added to series
--
There's no need to make the machine allow every possible sysbus
device. We can now just add xen-sysdev to the allowed list.
Cc: Stefano Stabellini
Cc: Anthony Perard
Cc: xen-de...@lists.xenproject.org
Cc: Juergen Gross
Signed-off-by: Eduardo Habkost
---
Changes series v1 -> v2:
* New patch ad
The only user-creatable sysbus devices in qemu-system-x86_64 are
amd-iommu, intel-iommu, and xen-backend. xen-backend is handled
by xen_set_dynamic_sysbus(), so we only need to add amd-iommu and
intel-iommu.
Cc: "Michael S. Tsirkin"
Cc: Marcel Apfelbaum
Signed-off-by: Eduardo Habkost
---
Chang
Dear Andrew,
A month passed, and the maintainers didn't gave a damn about raspi3 support
in qemu. Any ideas?
On Wed, Oct 25, 2017 at 10:52 AM, bzt bzt wrote:
> Hi Andrew!
>
> On Tue, Oct 24, 2017 at 6:44 PM, Andrew Baumann <
> andrew.baum...@microsoft.com> wrote:
> [...]
>
>> I see. The address
On Sat, 25 Nov 2017 13:16:05 -0200
Eduardo Habkost wrote:
> The existing has_dynamic_sysbus flag makes the machine accept
> every user-creatable sysbus device type on the command-line.
> Replace it with a list of allowed device types, so machines can
> easily accept some sysbus devices while reje
On Sat, 25 Nov 2017 13:16:08 -0200
Eduardo Habkost wrote:
> TYPE_SPAPR_PCI_HOST_BRIDGE is the only dynamic sysbus device not
> rejected by ppc_spapr_reset(), so it can be the only entry on the
> allowed list.
>
So we don't need the code that rejects other sysbus devices anymore, right ?
We shou
On 25 November 2017 at 16:43, bzt bzt wrote:
> Dear Andrew,
>
> A month passed, and the maintainers didn't gave a damn about raspi3 support
> in qemu. Any ideas?
Sorry this patch fell through the cracks, but it looked to me
to be in the state "patch got code review comments, waiting for
submitter
On Sat, 25 Nov 2017 13:16:07 -0200
Eduardo Habkost wrote:
> platform_bus_create_devtree() already rejects all dynamic sysbus
> devices except TYPE_ETSEC_COMMON, so register it as the only
> allowed dynamic sysbus device for the ppce500 machine-type.
>
Maybe drop the code that rejects unsupporte
God day Edgar,
Thank you very much for reviewing and testing the series!
Best regards,
Francisco Iglesias
On Friday, 24 November 2017, Edgar E. Iglesias
wrote:
> On Fri, Nov 24, 2017 at 10:29:25PM +0100, Francisco Iglesias wrote:
> > Hi,
> >
> > This patch series is an attempt to add support f
Public bug reported:
I start QEMU with qemu-system-arm-m 130 -M n800 -kernel zImage.1 -mtdblock
maemo.img -append "root=/dev/mtdblock3 rootfstype=jffs2"
On QEMU 1.2.0 see "NOKIA" logo and then desktop appears, but on 1.5.0 and newer
(including latest versions) I see only white screen and no sign
UPD: Maemo will boot on the second attempt if I reset the emulator
manually.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1734474
Title:
Maemo does not boot on emulated N800
Status in QEMU:
New
That's a regression, but unfortunately the n800 boards aren't really
maintained (I don't have any test images to hand, and the hardware is
long-gone these days). You could try a git bisect to see what commit
broke, if you want to investigate.
--
You received this bug notification because you are
Hi,
On 2017/11/24 14:30, Yang Zhong wrote:
> Since there are some issues in memory alloc/free machenism
> in glibc for little chunk memory, if Qemu frequently
> alloc/free little chunk memory, the glibc doesn't alloc
> little chunk memory from free list of glibc and still
> allocate from OS, which
22 matches
Mail list logo
