Hi Sebastian,
On Mon, Oct 28, 2013 at 9:56 AM, Sebastian Macke sebast...@macke.de wrote:
On 25/10/2013 5:21 PM, Jia Liu wrote:
On Fri, Oct 25, 2013 at 7:23 AM, Sebastian Macke sebast...@macke.de
wrote:
On 22/10/2013 8:47 PM, Jia Liu wrote:
Hi Sebastian,
On Tue, Oct 22, 2013 at 8:12 AM,
sun4m.c and sun4u.c both define a qdev named TYPE_OPENPROM. As far as I
can tell, they differ only in the name of their memory region.
If they ever get linked into the same executable,
type_register_internal() will reject the second one. But they aren't,
so this isn't a bug. Is it bad style?
Le Friday 04 Oct 2013 à 16:31:56 (+0200), Max Reitz a écrit :
On 2013-10-02 14:39, Benoît Canet wrote:
It must be applied on top of block: Add
BlockDriver.bdrv_check_ext_snapshot.
This patchset create a block driver implementing a quorum using total qemu
disk
images. Writes are mirrored
On 2013-10-28 20:18, Stefan Weil wrote:
Am 18.09.2013 09:48, schrieb Jan Kiszka:
On 2013-09-18 09:26, Peter Maydell wrote:
[...]
And gcc's documentation of the 'noreturn' attribute specifically
says it does not affect the exceptional path where the function
returns via longjmp.
OK, that is
This patch set add one sheepdog specific option for qemu-img to control
redundancy.
This patch set is on top of Kevin's block tree.
Liu Yuan (2):
sheepdog: refactor do_sd_create()
sheepdog: support user-defined redundancy option
block/sheepdog.c | 110
We can actually use BDRVSheepdogState *s to pass most of the parameters.
Cc: Kevin Wolf kw...@redhat.com
Cc: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Liu Yuan namei.u...@gmail.com
---
block/sheepdog.c | 37 +++--
1 file changed, 15 insertions(+), 22
Sheepdog support two kinds od redundancy, full replication and erasure coding.
# create a fully replicated vdi with x copies
-o redundancy=x (1 = x = SD_MAX_COPIES)
# create a erasure coded vdi with x data strips and y parity strips
-o redundancy=x:y (x must be one of {2,4,8,16} and 1 = y
We can actually use BDRVSheepdogState *s to pass most of the parameters.
Cc: Kevin Wolf kw...@redhat.com
Cc: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Liu Yuan namei.u...@gmail.com
---
block/sheepdog.c | 37 +++--
1 file changed, 15 insertions(+), 22
v2:
- fix a typo in comment and commit log
This patch set add one sheepdog specific option for qemu-img to control
redundancy.
This patch set is on top of Kevin's block tree.
Liu Yuan (2):
sheepdog: pass copy_policy in the request
sheepdog: refactor do_sd_create()
block/sheepdog.c | 45
Currently copy_policy isn't used. Recent sheepdog supports erasure coding, which
make use of copy_policy internally, but require client explicitly passing
copy_policy from base inode to newly creately inode for snapshot related
operations.
If connected sheep daemon doesn't utilize copy_policy,
On Tue, Oct 29, 2013 at 04:23:33PM +0800, Liu Yuan wrote:
v2:
- fix a typo in comment and commit log
This patch set add one sheepdog specific option for qemu-img to control
redundancy.
This patch set is on top of Kevin's block tree.
Oops, please ignore this patch set because I formated
We can actually use BDRVSheepdogState *s to pass most of the parameters.
Cc: Kevin Wolf kw...@redhat.com
Cc: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Liu Yuan namei.u...@gmail.com
---
block/sheepdog.c | 37 +++--
1 file changed, 15 insertions(+), 22
Sheepdog support two kinds of redundancy, full replication and erasure coding.
# create a fully replicated vdi with x copies
-o redundancy=x (1 = x = SD_MAX_COPIES)
# create a erasure coded vdi with x data strips and y parity strips
-o redundancy=x:y (x must be one of {2,4,8,16} and 1 = y
v2:
- fix a typo in comment and commit log
This patch set add one sheepdog specific option for qemu-img to control
redundancy.
This patch set is on top of Kevin's block tree.
Liu Yuan (2):
sheepdog: refactor do_sd_create()
sheepdog: support user-defined redundancy option
Which version of make are you using? Recently, a bug with make 4.0 has
been discovered, please see this thread for a description and a work-
around:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg198719.html
--
You received this bug notification because you are a member of qemu-
devel-ml,
- Original Message -
From: Peter Lieven p...@kamp.de
To: Gleb Natapov g...@redhat.com, Vadim Rozenfeld vroze...@redhat.com,
qemu-devel@nongnu.org
Sent: Monday, October 28, 2013 6:50:31 PM
Subject: [Qemu-devel] kvm/hyper-v: obtaining client machine id
Hi,
do you know if it is possible
Il 28/10/2013 19:42, Michael S. Tsirkin ha scritto:
Hmm. Actually maybe there was an io error... is there
an easy way to find out?
This would be a *host* I/O error, so I doubt.
Yes, I know. Something like an out of range access on a disk
can trigger it perhaps?
Yes, that could
On Di, 2013-10-15 at 12:04 +0200, Gerd Hoffmann wrote:
Hi,
It's probably going to be a bit tough this time. We are pretty late in
the qemu 1.7 devel cycle, soft freeze today, and a big chunk of code
(ahci-tables-from qemu) which needs seabios support[1] is just about to
be pulled.
On Mon, Oct 21, 2013 at 12:08:44PM +0400, Dmitry Krivenok wrote:
Changes to v1:
1) Resolved names clash in include/net/eth.h
2) Reused is_multicast_ether_addr() from that header for MAC check.
Signed-off-by: Dmitry V. Krivenok krivenok.dmi...@gmail.com
---
include/net/eth.h | 6 +++---
On 29.10.2013 10:03, Vadim Rozenfeld wrote:
- Original Message -
From: Peter Lieven p...@kamp.de
To: Gleb Natapov g...@redhat.com, Vadim Rozenfeld vroze...@redhat.com,
qemu-devel@nongnu.org
Sent: Monday, October 28, 2013 6:50:31 PM
Subject: [Qemu-devel] kvm/hyper-v: obtaining client
Hi all,
this question might seem a bit weird, but does anyone see a good way to avoid
that Windows is able to boot inside qemu?
We have defined several profiles for different operation systems and I want
to avoid that someone chooses Linux and then installs Windows within
a VM. Reason is
Il 29/10/2013 10:48, Peter Lieven ha scritto:
Hi all,
this question might seem a bit weird, but does anyone see a good way to
avoid
that Windows is able to boot inside qemu?
We have defined several profiles for different operation systems and I want
to avoid that someone chooses Linux
On Wed, 16 Oct 2013 12:20:45 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 10:49:10AM +0200, Igor Mammedov wrote:
* simplify PCI address space mapping into system address space,
replacing code duplication in piix/q53 PCs with helper function
I think this does
On 29.10.2013 10:59, Paolo Bonzini wrote:
Il 29/10/2013 10:48, Peter Lieven ha scritto:
Hi all,
this question might seem a bit weird, but does anyone see a good way to
avoid
that Windows is able to boot inside qemu?
We have defined several profiles for different operation systems and I want
This patch adds support for a network backend based on netmap.
netmap is a framework for high speed packet I/O. You can use it
to build extremely fast traffic generators, monitors, software
switches or network middleboxes. Its companion software switch
VALE lets you interconnect virtual machines.
On Tue, Oct 29, 2013 at 11:08:56AM +0100, Igor Mammedov wrote:
On Wed, 16 Oct 2013 12:20:45 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 10:49:10AM +0200, Igor Mammedov wrote:
* simplify PCI address space mapping into system address space,
replacing code
Il 29/10/2013 11:11, Peter Lieven ha scritto:
On 29.10.2013 10:59, Paolo Bonzini wrote:
Il 29/10/2013 10:48, Peter Lieven ha scritto:
Hi all,
this question might seem a bit weird, but does anyone see a good way to
avoid
that Windows is able to boot inside qemu?
We have defined several
On Tue, Oct 29, 2013 at 11:19:54AM +0100, Paolo Bonzini wrote:
Il 29/10/2013 11:11, Peter Lieven ha scritto:
On 29.10.2013 10:59, Paolo Bonzini wrote:
Il 29/10/2013 10:48, Peter Lieven ha scritto:
Hi all,
this question might seem a bit weird, but does anyone see a good way to
avoid
On 29.10.2013 11:19, Paolo Bonzini wrote:
Il 29/10/2013 11:11, Peter Lieven ha scritto:
On 29.10.2013 10:59, Paolo Bonzini wrote:
Il 29/10/2013 10:48, Peter Lieven ha scritto:
Hi all,
this question might seem a bit weird, but does anyone see a good way to
avoid
that Windows is able to boot
Il 29/10/2013 11:40, Peter Lieven ha scritto:
The KVM signature should be at CPUID leaf 0x4100.
If I enable hyperv for all vServers the signature is at
KVM_CPUID_SIGNATURE_NEXT (0x4100) otherwise
at KVM_CPUID_SIGNATURE (0x0).
KVM_CPU_ID_SIGNATURE is 0x4000.
Does this matter to
On 29.10.2013 11:48, Paolo Bonzini wrote:
Il 29/10/2013 11:40, Peter Lieven ha scritto:
The KVM signature should be at CPUID leaf 0x4100.
If I enable hyperv for all vServers the signature is at
KVM_CPUID_SIGNATURE_NEXT (0x4100) otherwise
at KVM_CPUID_SIGNATURE (0x0).
On Mon, Oct 28, 2013 at 08:50:31AM +0100, Peter Lieven wrote:
Hi,
do you know if it is possible to obtain the client machine id of a Windows
vServer via
a Hyper-V hypercall? I would need an information to check vServer activations
against
our KMS.
Have not idea, sorry.
--
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this question might seem a bit weird, but does anyone see a good way to avoid
that Windows is able to boot inside qemu?
We have defined several profiles for different operation systems and I want
to avoid that someone
On Tue, 29 Oct 2013 12:22:09 +0200
Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 29, 2013 at 11:08:56AM +0100, Igor Mammedov wrote:
On Wed, 16 Oct 2013 12:20:45 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 10:49:10AM +0200, Igor Mammedov wrote:
*
On Tue, Oct 29, 2013 at 01:13:24PM +0200, Michael S. Tsirkin wrote:
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this question might seem a bit weird, but does anyone see a good way to
avoid
that Windows is able to boot inside qemu?
We have defined
On 29.10.2013 12:26, Gleb Natapov wrote:
On Tue, Oct 29, 2013 at 01:13:24PM +0200, Michael S. Tsirkin wrote:
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this question might seem a bit weird, but does anyone see a good way to avoid
that Windows is able to boot inside
On Tue, Oct 29, 2013 at 12:31:18PM +0100, Peter Lieven wrote:
On 29.10.2013 12:26, Gleb Natapov wrote:
On Tue, Oct 29, 2013 at 01:13:24PM +0200, Michael S. Tsirkin wrote:
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this question might seem a bit weird, but does
The block layer generally keeps the size of an image cached in
bs-total_sectors so that it doesn't have to perform expensive
operations to get the size whenever it needs it.
This doesn't work however when using a backend that can change its size
without qemu being aware of it, i.e. passthrough of
On Tue, Oct 29, 2013 at 11:08:56AM +0100, Igor Mammedov wrote:
On Wed, 16 Oct 2013 12:20:45 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 10:49:10AM +0200, Igor Mammedov wrote:
* simplify PCI address space mapping into system address space,
replacing code
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this question might seem a bit weird, but does anyone see a good way to avoid
that Windows is able to boot inside qemu?
We have defined several profiles for different operation systems and I want
to avoid that someone
Am 28.10.2013 um 20:01 hat Michael S. Tsirkin geschrieben:
From: Alexander Graf ag...@suse.de
When AHCI executes an asynchronous IDE command, it checked DRDY without
checking either DRQ or BSY. This sometimes caused interrupt to be sent
before command is actually completed.
This resulted
Am 26.10.2013 um 15:31 hat Max Reitz geschrieben:
Am 25.10.2013 02:15, schrieb Thibaut LAURENT:
Since commit 0ebd24e0a203cf2852c310b59fbe050190dc6c8c,
bdrv_open_common will throw an error when trying to open a file
read-only with the BDRV_O_COPY_ON_READ flag set.
Although BDRV_O_RDWR is
Il 29/10/2013 12:35, Kevin Wolf ha scritto:
The block layer generally keeps the size of an image cached in
bs-total_sectors so that it doesn't have to perform expensive
operations to get the size whenever it needs it.
This doesn't work however when using a backend that can change its size
On Tue, 2013-10-29 at 10:40 +0100, Peter Lieven wrote:
On 29.10.2013 10:03, Vadim Rozenfeld wrote:
- Original Message -
From: Peter Lieven p...@kamp.de
To: Gleb Natapov g...@redhat.com, Vadim Rozenfeld
vroze...@redhat.com, qemu-devel@nongnu.org
Sent: Monday, October 28, 2013
Am 29.10.2013 um 13:02 hat Paolo Bonzini geschrieben:
Il 29/10/2013 12:35, Kevin Wolf ha scritto:
The block layer generally keeps the size of an image cached in
bs-total_sectors so that it doesn't have to perform expensive
operations to get the size whenever it needs it.
This doesn't
On Tue, Oct 29, 2013 at 01:26:59PM +0200, Gleb Natapov wrote:
On Tue, Oct 29, 2013 at 01:13:24PM +0200, Michael S. Tsirkin wrote:
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this question might seem a bit weird, but does anyone see a good way to
avoid
On Tue, Oct 29, 2013 at 02:17:10PM +0200, Michael S. Tsirkin wrote:
On Tue, Oct 29, 2013 at 01:26:59PM +0200, Gleb Natapov wrote:
On Tue, Oct 29, 2013 at 01:13:24PM +0200, Michael S. Tsirkin wrote:
On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote:
Hi all,
this
* simplify PCI address space mapping into system address space,
replacing code duplication in piix/q53 PCs with a helper function
* add fw_cfg 'etc/pcimem64-minimum-address' to allow QEMU reserve
additional address space before 64-bit PCI hole. Which will be
need for reserving memory
'etc/pcimem64-minimum-address' will allow QEMU to tell BIOS
where PCI memory address space mapping could start in high memory.
Allowing BIOS to start mapping 64-bit PCI BARs at address where it
wouldn't conflict with other mappings QEMU might place before it.
That permits QEMU to reserve extra
From: Michael S. Tsirkin m...@redhat.com
With a help of negative memory region priority PCI address space
is mapped underneath RAM regions effectively catching every access
to addresses not mapped by any other region.
It simplifies PCI address space mapping into system address space.
From 89de52ee03f68cef1f3343d3275162427ec22ded Mon Sep 17 00:00:00 2001
From: Tom Musta tommu...@gmail.com
Date: Tue, 29 Oct 2013 07:52:19 -0500
Subject:
To: qemu-...@nongnu.org
This is the third series of patches to add PowerPC VSX emulation support
to QEMU.
This series adds the floating point
The comment preceding the float64_to_uint64 routine suggests that
the implementation is broken. And this is, indeed, the case.
This patch properly implements the conversion of a 64-bit floating
point number to an unsigned, 64 bit integer.
This contribution can be licensed under either the
This patch adds the float32_to_uint64() routine, which converts a
32-bit floating point number to an unsigned 64 bit number.
This contribution can be licensed under either the softfloat-2a or -2b
license.
V2: Reduced patch to just this single routine per feedback from Peter
Maydell.
The fload_invalid_op_excp() function sets assorted invalid
operation status bits. However, it also implicitly modifies
the FPRF field of the PowerPC FPSCR. Many VSX instructions
set invalid operation bits but do not alter FPRF. Thus the
function is more generally useful if the setting of the
This patch adds the floating point addition and subtraction
instructions defined by V2.06 of the PowerPC ISA: xssubdp,
xvsubdp and xvsubsp.
V2: re-implemented helper macro and combined add and substract.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 51
This patch adds general support that will be used by the VSX helper
routines:
- a union describing the various VSR subfields.
- access routines to get and set VSRs
- VSX decoders
- a general routine to generate a handler that invokes a VSX
helper.
Signed-off-by: Tom Musta
This patch adds the VSX floating point divide instructions defined
by V2.06 of the PowerPC ISA: xsdivdp, xvdivdp, xvdivsp.
V2: re-implemented the VSX_DIV macro.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 49 +++
This patch adds the VSX floating point multiply instructions defined
by V2.06 of the PowerPC ISA: xsmuldp, xvmuldp, xvmulsp.
V2: re-implemented VSX_MUL macro.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 46 ++
This patch adds the VSX floating point reciprocal estimate instructions
defined by V2.06 of the PowerPC ISA: xsredp, xvredp, xvresp.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 35 +++
target-ppc/helper.h |3 +++
This patch adds the VSX floating point square root instructions
defined by V2.06 of the PowerPC ISA: xssqrtdp, xvsqrtdp, xvsqrtsp.
V2: re-implemented the VSX_SQRT macro.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 44
This patch adds the VSX floating point test for software square
root instructions defined by V2.06 of the PowerPC ISA: xstsqrtdp,
xvtsqrtdp, xvtsqrtsp.
V2: (a) using locally implemented ppc_float*_get_unbiased_exp
routines (b) eliminated dependency on float*_is_denormal().
Signed-off-by: Tom
Hi,
1. When QEMU for MIPS support watchpoint debug facility? Any hint or guide
to implement that function?
2. qemu-system-mipsel -M malta -kernel vmlinux-2.6.26-1-4kc-malta -hda
debian_lenny_mipsel_small.qcow2 -append root=/dev/hda1 console=ttyS0
kgdboc=ttyS0,115200 kgdbwait -nographic -serial
This patch adds the VSX floating point test for software divide
instructions defined by V2.06 of the PowerPC ISA: xstdivdp, xvtdivdp,
and xvtdivsp.
V2: added ppc_float*_get_unbiased_exp() routines (pulled back from
softfloat). Eliminated dependency on float*_is_denormalized()
routines.
This patch adds the VSX floating point multiply/add instructions
defined by V2.06 of the PowerPC ISA:
- xsmaddadp, xvmaddadp, xvmaddasp
- xsmaddmdp, xvmaddmdp, xvmaddmsp
- xsmsubadp, xvmsubadp, xvmsubasp
- xsmsubmdp, xvmsubmdp, xvmsubmsp
- xsnmaddadp, xvnmaddadp, xvnmaddasp
-
This patch adds the VSX scalar floating point compare ordered
and unordered instructions.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 39 +++
target-ppc/helper.h |2 ++
target-ppc/translate.c |4
3 files
This patch adds the VSX instructions that convert between floating
point formats: xscvdpsp, xscvspdp, xvcvdpsp, xvcvspdp.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 46 ++
target-ppc/helper.h |4
This patch adds the VSX floating point maximum and minimum
instructions:
- xsmaxdp, xvmaxdp, xvmaxsp
- xsmindp, xvmindp, xvminsp
Because of the Power ISA definitions of maximum and minimum
on various boundary cases, the standard softfloat comparison
routines (e.g. float64_lt) do not work as
On (Fri) 04 Oct 2013 [21:18:02], Amit Shah wrote:
Hi Anthony,
Please pull to receive a fix for a segfault in the char layer. The
patches have been on the list for a week, and Gerd has reviewed them.
(I'm overloading the virtio-serial git tree for this series, haven't
gotten around to
This patch adds the VSX floating point compare vector instructions:
- xvcmpeqdp[.], xvcmpgedp[.], xvcmpgtdp[.]
- xvcmpeqsp[.], xvcmpgesp[.], xvcmpgtsp[.]
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 57 +++
This patch adds the VSX Integer Conversion instructions defined by
V2.06 of the PowerPC ISA:
- xscvdpsxds, xscvdpsxws, xscvdpuxds, xscvdpuxws
- xvcvdpsxds, xvcvdpsxws, xvcvdpuxds, xvcvdpuxws
- xvcvspsxds, xvcvspsxws, xvcvspuxds, xvcvspuxws
- xscvsxddp, xscvuxddp
- xvcvsxddp, xscvsxwdp,
This patch adds the VSX Round to Floating Point Integer instructions:
- xsrdpi, xsrdpic, xsrdpim, xsrdpip, xsrdpiz
- xvrdpi, xvrdpic, xvrdpim, xvrdpip, xvrdpiz
- xvrspi, xvrspic, xvrspim, xvrspip, xvrspiz
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 68
This patch adds the VSX floating point reciprocal square root
estimate instructions defined by V2.06 of the PowerPC ISA: xsrsqrtedp,
xvrsqrtedp, xvrsqrtesp.
V2: re-implemented VSX_RSQRTE macro.
Signed-off-by: Tom Musta tommu...@gmail.com
---
target-ppc/fpu_helper.c | 45
Juan Quintela quint...@redhat.com wrote:
Hi
Please, send any topic that you are interested in covering.
As there are no topics, no call (lots of stuff got discussed on kvm forum)
See you in two weeks.
On 10/29/13 11:50, Peter Lieven wrote:
On 29.10.2013 11:48, Paolo Bonzini wrote:
Il 29/10/2013 11:40, Peter Lieven ha scritto:
The KVM signature should be at CPUID leaf 0x4100.
If I enable hyperv for all vServers the signature is at
KVM_CPUID_SIGNATURE_NEXT (0x4100) otherwise
at
On 29 October 2013 07:57, Markus Armbruster arm...@redhat.com wrote:
sun4m.c and sun4u.c both define a qdev named TYPE_OPENPROM. As far as I
can tell, they differ only in the name of their memory region.
If they ever get linked into the same executable,
type_register_internal() will reject
The BIOS that we ship in 1.7 does not use pci info
from host and so far isn't going to use it.
Taking in account problems it caused see 9604f70fdf and
to avoid future incompatibility issues, it's safest to
disable that interface by default for all machine types
including 1.7 as it was never
On Di, 2013-10-29 at 15:35 +0100, Igor Mammedov wrote:
The BIOS that we ship in 1.7 does not use pci info
from host and so far isn't going to use it.
Taking in account problems it caused see 9604f70fdf and
to avoid future incompatibility issues, it's safest to
disable that interface by
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
---
hw/usb/dev-network.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/usb/dev-network.c b/hw/usb/dev-network.c
index 660d774..4c532b7 100644
--- a/hw/usb/dev-network.c
+++ b/hw/usb/dev-network.c
@@ -637,7 +637,6 @@ typedef struct
I am trying to prevent write from DomU for particular sector of hardisk
which is passed through QEMU device.
I am putting an error condition in ide.c using API
ide_handle_write_error(s, -ret, BM_STATUS_ERROR) called from
ide_write_dma_cb, however DomU is still going ahead and writing to those
On Tue, Oct 29, 2013 at 01:57:33PM +0100, Igor Mammedov wrote:
* simplify PCI address space mapping into system address space,
replacing code duplication in piix/q53 PCs with a helper function
* add fw_cfg 'etc/pcimem64-minimum-address' to allow QEMU reserve
additional address space
On Tue, Oct 29, 2013 at 03:35:07PM +0100, Igor Mammedov wrote:
The BIOS that we ship in 1.7 does not use pci info
from host and so far isn't going to use it.
Taking in account problems it caused see 9604f70fdf and
to avoid future incompatibility issues, it's safest to
disable that interface
On Mon, Oct 21, 2013 at 03:44:46PM +0400, Fedorov Sergey wrote:
After our discussion about this patch I decided to keep my patch in
our branch until rebase onto a new release. Recently I have rebased
our branch onto v1.5.3 and reverted my patch. Then I face an issue
when using user-mode
On Tue, 29 Oct 2013 17:10:47 +0200
Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 29, 2013 at 01:57:33PM +0100, Igor Mammedov wrote:
* simplify PCI address space mapping into system address space,
replacing code duplication in piix/q53 PCs with a helper function
* add fw_cfg
On Tue, Oct 29, 2013 at 03:35:07PM +0100, Igor Mammedov wrote:
The BIOS that we ship in 1.7 does not use pci info
from host and so far isn't going to use it.
Taking in account problems it caused see 9604f70fdf and
to avoid future incompatibility issues, it's safest to
disable that interface
Il 29/10/2013 16:55, BALATON Zoltan ha scritto:
On Tue, 29 Oct 2013, Laszlo Ersek wrote:
I don't know what I'm talking about. But:
Neither do I but...
- Windows' ACPI parser is super cranky. You could pass in a custom (but
standardized) ACPI table on the command line (-acpitable) that
Ping!
Hu Tao hu...@cn.fujitsu.com writes:
Hi All,
I know it's been a long time since this thread. But qemu 1.7 is
releasing, do you have any consensus on this?
Thanks.
On Tue, 29 Oct 2013, Laszlo Ersek wrote:
I don't know what I'm talking about. But:
Neither do I but...
- Windows' ACPI parser is super cranky. You could pass in a custom (but
standardized) ACPI table on the command line (-acpitable) that only
triggers some warnings in Linux's port of ACPICA,
Commit 684b254 forgot to update it.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
tests/qemu-iotests/051.out | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/051.out b/tests/qemu-iotests/051.out
index 2839e32..15deef6 100644
--- a/tests/qemu-iotests/051.out
From: Markus Armbruster arm...@redhat.com
Signed-off-by: Markus Armbruster arm...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
---
hw/intc/apic_common.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/hw/intc/apic_common.c b/hw/intc/apic_common.c
index
From: Markus Armbruster arm...@redhat.com
In an ideal world, machines can be built by wiring devices together
with configuration, not code. Unfortunately, that's not the world we
live in right now. We still have quite a few devices that need to be
wired up by code. If you try to device_add
From: Markus Armbruster arm...@redhat.com
Signed-off-by: Markus Armbruster arm...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
---
qom/cpu.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/qom/cpu.c b/qom/cpu.c
index 09c15e6..6e0d54e 100644
---
From: Markus Armbruster arm...@redhat.com
A VT82C686B southbridge has multiple functions. We model each
function as a separate qdev. One of them need some special wiring set
up in mips_fulong2e_init() to work: the ISA bridge at 05.0.
The IDE controller at 05.1 (via-ide) has always had
From: Markus Armbruster arm...@redhat.com
Such devices have always been unavailable and omitted from the list of
available devices shown by device_add help. Until commit 18b6dad
silently broke the former, setting up nasty traps for unwary users,
like this one:
$ qemu-system-x86_64
From: Markus Armbruster arm...@redhat.com
An ICH9 southbridge contains several PCI devices, some of them with
multiple functions. We model each function as a separate qdev. Two
of them need some special wiring set up in pc_q35_init() to work: the
LPC controller at 00:1f.0, and the SMBus
Ping
http://patchwork.ozlabs.org/patch/281527/
From: Petar Jovanovic
Sent: Tuesday, October 22, 2013 5:13 PM
To: Petar Jovanovic; qemu-devel@nongnu.org
Cc: aurel...@aurel32.net; riku.voi...@linaro.org; peter.mayd...@linaro.org
Subject: RE: [PATCH]
On 10/28/2013 11:22 PM, Wenchao Xia wrote:
MONITOR_EVENT seems tide to monitor too much, since it will be present
in qapi-schema, I think Q_EVENT_ or QMP_EVENT_KIND would be better?
I don't have a strong enough opinion on the bikeshed color.
MONITOR_EVENT implies the event is always
From: Markus Armbruster arm...@redhat.com
Many PCI host bridges consist of a sysbus device and a PCI device.
You need both for the thing to work. Arguably, these bridges should
be modelled as a single, composite devices instead of pairs of
seemingly independent devices you can only use together,
From: Markus Armbruster arm...@redhat.com
A PIIX3/PIIX4 southbridge has multiple functions. We model each
function as a separate qdev. Two of them need some special wiring set
up in pc_init1() or mips_malta_init() to work: the ISA bridge at 01.0,
and the SMBus controller at 01.3.
The IDE
Hi Christoffer,
Not related to the patch, for edge type of interrupt, will setting bit in
ICD_SPENDR generate interrupt?
Thanks
-Bharat
-Original Message-
From: Christoffer Dall [mailto:christoffer.d...@linaro.org]
Sent: Wednesday, October 23, 2013 8:57 PM
To:
On 10/29/2013 10:08 AM, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
A PIIX3/PIIX4 southbridge has multiple functions. We model each
function as a separate qdev. Two of them need some special wiring set
up in pc_init1() or mips_malta_init() to work: the ISA bridge at
1 - 100 of 201 matches
Mail list logo
