On Sat, Nov 23, 2013 at 3:17 AM, Peter Maydell peter.mayd...@linaro.org wrote:
Device trees created with create_device_tree() may not have any
entries in their reservemap, because the FDT API requires that the
reservemap is completed before any FDT nodes are added, and
create_device_tree()
commit bdf523e6923f1e667055e947e71fc600549cefae
configure: Add config.status to recreate the current configuration
moved current configure flags to config.status
This makes sense, but this makes it harder to bisect problems that
trigger with a specific set of flags only, since old configure
--iasl option was added to CC option parsing section by mistake,
it's not effective there and attempts to use cause
an 'unknown option' error.
Fix this up.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Useful for platforms with a broken IASL.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
configure | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 0592ba7..d0a0abe 100755
--- a/configure
+++ b/configure
@@ -1080,6 +1080,7 @@ echo
Am 22.11.2013 13:51, schrieb Gerd Hoffmann:
Hi,
'make check' for MinGW cross builds needs an installation of wine to run
the resulting exe files.
I don't think it is a good idea to run tests for cross builds by
default.
cheers,
Gerd
Why not? In this case (MinGW), setting up cross
On Fri, Nov 22, 2013 at 06:14:46PM +0100, Igor Mammedov wrote:
On Thu, 21 Nov 2013 16:38:47 +0200
Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 21, 2013 at 03:21:37PM +0100, Igor Mammedov wrote:
On Thu, 21 Nov 2013 11:42:02 +0200
Michael S. Tsirkin m...@redhat.com wrote:
[...]
Am 24.11.2013 10:37, schrieb Michael S. Tsirkin:
commit bdf523e6923f1e667055e947e71fc600549cefae
configure: Add config.status to recreate the current configuration
moved current configure flags to config.status
This makes sense, but this makes it harder to bisect problems that
trigger
On Thu, Nov 21, 2013 at 10:40:43PM +0100, Erik Rull wrote:
Marcel Apfelbaum wrote:
On Thu, 2013-11-21 at 22:20 +0100, Erik Rull wrote:
Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
On Thu, Nov 21, 2013 at 09:33:20PM +0200, Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
Test 2:
- runs only if iasl is installed on the host machine.
- the test plan:
1. Dumps
On Sun, 2013-11-24 at 13:33 +0200, Michael S. Tsirkin wrote:
On Thu, Nov 21, 2013 at 09:33:20PM +0200, Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
Test 2:
- runs only if
On Sun, Nov 24, 2013 at 01:37:09PM +0200, Marcel Apfelbaum wrote:
On Sun, 2013-11-24 at 13:33 +0200, Michael S. Tsirkin wrote:
On Thu, Nov 21, 2013 at 09:33:20PM +0200, Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and
On Sun, 2013-11-24 at 11:52 +0200, Michael S. Tsirkin wrote:
--iasl option was added to CC option parsing section by mistake,
it's not effective there and attempts to use cause
an 'unknown option' error.
Fix this up.
Now it works...
Tested-by: Marcel Apfelbaum marce...@redhat.com
On Sun, 2013-11-24 at 11:52 +0200, Michael S. Tsirkin wrote:
Useful for platforms with a broken IASL.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
configure | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 0592ba7..d0a0abe 100755
On Sun, Nov 24, 2013 at 03:04:04PM +0200, Marcel Apfelbaum wrote:
On Sun, 2013-11-24 at 11:52 +0200, Michael S. Tsirkin wrote:
Useful for platforms with a broken IASL.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
configure | 3 ++-
1 file changed, 2 insertions(+), 1
Am 24.11.2013 14:42, schrieb Michael S. Tsirkin:
On Sun, Nov 24, 2013 at 03:04:04PM +0200, Marcel Apfelbaum wrote:
On Sun, 2013-11-24 at 11:52 +0200, Michael S. Tsirkin wrote:
Useful for platforms with a broken IASL.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
configure | 3 ++-
Hi Mario,
Can you check the offload settings of the tap device that is connected to guest?
Run “ethtool -k tap-solaripub”.
On the guest. Raise the log verbosity by going to device manager - NetKVM
device - Advanced tab - Logging.Level and changing it to 4. Use DebugView to
record the driver
Public bug reported:
It works fine when not using kvm and it does also work fine when using
oneshot mode.
Tested with qemu 1.6.1 (commit
62ecc3a0e3c77a4944c92a02dd7fae2ab1f2290d).
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because
Am 24.11.2013 10:52, schrieb Michael S. Tsirkin:
--iasl option was added to CC option parsing section by mistake,
it's not effective there and attempts to use cause
an 'unknown option' error.
Fix this up.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
configure | 4 ++--
1 file
On Sun, Nov 24, 2013 at 02:54:51PM +0100, Stefan Weil wrote:
Am 24.11.2013 14:42, schrieb Michael S. Tsirkin:
On Sun, Nov 24, 2013 at 03:04:04PM +0200, Marcel Apfelbaum wrote:
On Sun, 2013-11-24 at 11:52 +0200, Michael S. Tsirkin wrote:
Useful for platforms with a broken IASL.
On Sun, Nov 24, 2013 at 05:39:58PM +0200, Michael S. Tsirkin wrote:
On Sun, Nov 24, 2013 at 02:54:51PM +0100, Stefan Weil wrote:
Am 24.11.2013 14:42, schrieb Michael S. Tsirkin:
On Sun, Nov 24, 2013 at 03:04:04PM +0200, Marcel Apfelbaum wrote:
On Sun, 2013-11-24 at 11:52 +0200, Michael S.
This series simplifies kvm_cpu_fill_host() and
kvm_check_features_against_host() to simply use FeatureWord feature_word_info
loops to fill/check feature words.
The initial motivation for this was to avoid hacks involving the host CPU
class on the forthcoming conversion of CPU models to be X86CPU
Those host_cpuid() calls are useless. They are leftovers from when the
old code using host_cpuid() was removed.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
target-i386/cpu.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index
Now that the kvm_cpu_fill_host() code is simplified, we can simply set
the feature word array using a simple loop.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
target-i386/cpu.c | 23 +++
1 file changed, 7 insertions(+), 16 deletions(-)
diff --git
There's no need to check level (CPUID[0].EAX) before calling
kvm_arch_get_supported_cpuid(s, 0x7, 0, R_EBX), because:
* The kernel won't return any entry for CPUID 7 if CPUID[0].EAX is 7
(See kvm_dev_ioctl_get_supported_cpuid() on the kernel code);
* kvm_arch_get_supported_cpuid() will
There's no need to check CPU xlevel2 before calling
kvm_arch_get_supported_cpuid(s, 0xC001, 0, R_EDX), because:
* The kernel won't return any entry for 0xC000 if host CPU vendor
is not Centaur (See kvm_dev_ioctl_get_supported_cpuid() on the kernel
code)
* Similarly, the kernel
There's no need to check CPU vendor before calling
kvm_arch_get_supported_cpuid(s, 0xC000, 0, R_EAX), because:
* The kernel won't return any entry for 0xC000 if host CPU vendor
is not Centaur (See kvm_dev_ioctl_get_supported_cpuid() on the kernel
code);
*
We don't need the ft[] array on kvm_check_features_against_host()
anymore, as we can simply use the feature_word_info[] array, that has
everything we need.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
target-i386/cpu.c | 41 -
1 file changed, 8
Reorder the code so all the code that sets x86_cpu_def-features is at
the end of the function.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
target-i386/cpu.c | 24 +---
1 file changed, 9 insertions(+), 15 deletions(-)
diff --git a/target-i386/cpu.c
As now kvm_cpu_fill_host() will simply fill the x86_def_t.features array
with the results of kvm_arch_get_supported_cpuid() calls, we can simply
call kvm_arch_get_supported_cpuid() directly.
Note how kvm_check_features_against_host() and filter_features_for_kvm()
are getting very similar.
On 11/10/13 2:31 AM, Gerd Hoffmann wrote:
On Do, 2013-10-10 at 21:17 +0200, Sebastian Herbszt wrote:
Andreas Färber wrote:
Same for http://patchwork.ozlabs.org/patch/273758/ - vgabios seems to
be falling through the cracks...
Andreas
Is this patch still required?
I was under the impression
This resolves the build issue with building the ROMs on OpenBSD on x86 archs.
As of OpenBSD 5.3 the compiler builds PIE binaries by default and thus the
whole OS/packages and so forth. The ROMs need to have PIE disabled. This
is my initial attempt at trying to get somehting upstream so that QEMU
Am 24.11.2013 17:48, schrieb Michael S. Tsirkin:
On Sun, Nov 24, 2013 at 05:39:58PM +0200, Michael S. Tsirkin wrote:
On Sun, Nov 24, 2013 at 02:54:51PM +0100, Stefan Weil wrote:
Am 24.11.2013 14:42, schrieb Michael S. Tsirkin:
On Sun, Nov 24, 2013 at 03:04:04PM +0200, Marcel Apfelbaum wrote:
Everything before CPU_COMMON in the structure is cleared as part of a
CPU reset. This included the features flag, which indicates whether SH4A
instructions are supported or not. As a result, a CPU reset downgraded
the CPU from an SH4A to an SH4.
Signed-off-by: Bobby Bingham koor...@koorogi.info
Hi! My first qemu devel mailing list message!!!
Thank you... your sincery suppport
From: Paul Mackerras pau...@samba.org
This makes sure that all NUMA memory blocks reside within RAM or
have zero length.
Reviewed-by: Thomas Huth th...@linux.vnet.ibm.com
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
Changes:
V6: fixed mistype
---
This is a bugfix for:
-m 500
-smp
The SPAPR specification says that the RMA starts at the LPAR's logical
address 0 and is the first logical memory block reported in
the LPAR’s device tree.
So SLOF only maps the first block and that block needs to span
the full RMA.
This makes sure that the RMA area is where SLOF expects it.
This fixes a bug in patch#1 and mistype in patch#2, details are in
the commit messages.
Alexey Kardashevsksy (1):
spapr: make sure RMA is in first mode of first memory node
Paul Mackerras (1):
spapr: limit numa memory regions by ram size
hw/ppc/spapr.c | 35
Bryant,
I found that there is some conflict in qemu-options.hx between your patch
and
qemu-1.7.0-rc1.tar.bz2http://wiki.qemu-project.org/download/qemu-1.7.0-rc1.tar.bz2.
What QEMU version does this patch base on? Thanks.
Quan Xu
Intel
Since modern POWER7/POWER8 chips can have more that 256 CPU threads
(2000 actually), remove this check from smp_parse.
The CPUs number is still checked against machine-max_cpus and this check
should be enough not to break other archs.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
vl.c
From: Zhouy zhouyuan.f...@cn.fujitsu.com
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini pbonz...@redhat.com, Anthony Liguori
anth...@codemonkey.ws,
Andreas F?rber afaer...@suse.de
Subject: Re: [Qemu-devel] [PATCH] hw/gpio/max7310.c : add the
reset-pin in Max7310 and the GPIO
On 11/06/2013 09:04 PM, Juan Quintela wrote:
Hi
[v2]
In this version:
- fixed all the comments from last versions (thanks Eric)
- kvm migration bitmap is synchronized using bitmap operations
- qemu bitmap - migration bitmap is synchronized using bitmap operations
If bitmaps are not properly
On 11/06/2013 11:49 PM, Paolo Bonzini wrote:
Il 06/11/2013 15:37, Gerd Hoffmann ha scritto:
- vga ram by default is not aligned in a page number multiple of
64,
it could be optimized. Kraxel? It syncs the kvm bitmap at least
1 a second or so? bitmap is only 2048 pages (16MB by default). We
On 11/25/2013 02:15 PM, Michael R. Hines wrote:
On 11/06/2013 09:04 PM, Juan Quintela wrote:
Hi
[v2]
In this version:
- fixed all the comments from last versions (thanks Eric)
- kvm migration bitmap is synchronized using bitmap operations
- qemu bitmap - migration bitmap is synchronized using
On So, 2013-11-24 at 15:35 -0500, Brad Smith wrote:
On 11/10/13 2:31 AM, Gerd Hoffmann wrote:
On Do, 2013-10-10 at 21:17 +0200, Sebastian Herbszt wrote:
Andreas Färber wrote:
Same for http://patchwork.ozlabs.org/patch/273758/ - vgabios seems to
be falling through the cracks...
Andreas
On So, 2013-11-24 at 11:21 +0100, Stefan Weil wrote:
Am 22.11.2013 13:51, schrieb Gerd Hoffmann:
Hi,
'make check' for MinGW cross builds needs an installation of wine to run
the resulting exe files.
I don't think it is a good idea to run tests for cross builds by
default.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
hw/net/spapr_llan.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/net/spapr_llan.c b/hw/net/spapr_llan.c
index 1bd6f50..229de00 100644
--- a/hw/net/spapr_llan.c
+++ b/hw/net/spapr_llan.c
@@ -29,6 +29,7 @@
#include hw/qdev.h
This changes VIO bridge fw name from spapr-vio-bridge to vdevice and
vscsi/veth node names from QEMU object names to VIO specific device tree
names.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
hw/ppc/spapr_vio.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/ppc/spapr_vio.c
This adds bootindex support for sPAPR. SLOF does not support this yet.
Alexey Kardashevskiy (5):
boot: extend get_boot_devices_list() to ignore suffixes
machine: introduce get_fw_dev_path() callback
spapr-llan: add to boot device list
spapr-vio: fix firmware names
spapr: define
As suffixes do not make sense for sPAPR's device tree and
there is no way to filter them out on the BusState::get_fw_dev_path
level, let's add an ability for the external caller to specify
whether to apply suffixes or not.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
hw/nvram/fw_cfg.c
This introduces a get_fw_dev_path() callback.
This fixes SCSI disks device node names (which are wildcard nodes in
the device-tree).
This fixes PHB name from pci to pci@ where is a BUID as
there is no bus on top of sPAPRPHBState where PHB firmware name could
be fixed using the
QEMU supports firmware names for all devices in the QEMU tree but
sometime the exact format differs from what sPAPR platform uses.
This introduces a callback to let a machine fix device tree path names.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
hw/core/qdev.c | 15
On 11/22/2013 07:36 PM, Paolo Bonzini wrote:
Il 22/11/2013 12:29, Lei Li ha scritto:
During the page flipping migration, ram page of source guest would
be flipped to the destination, that's why the source guest can not
be resumed. AFAICT, the page flipping migration may fail at the
connection
Michael S. Tsirkin m...@redhat.com writes:
[...]
Here this made me think of the following question:
should not memory available on boot be listed in CMOS?
Let's assume new BIOS gets interrupt telling it there's new memory.
It clears the interrupt and then system is reset.
Will system after
On 11/25/2013 06:03 AM, Bobby Bingham wrote:
Everything before CPU_COMMON in the structure is cleared as part of a
CPU reset. This included the features flag, which indicates whether SH4A
instructions are supported or not. As a result, a CPU reset downgraded
the CPU from an SH4A to an SH4.
54 matches
Mail list logo
