The binary qemu is now called qemu-system-i386.
QEMU provides more than one binary since several years.
Here is the list for system emulation:
qemu-system-alpha, qemu-system-arm, qemu-system-cris, qemu-system-i386,
qemu-system-lm32, qemu-system-m68k, qemu-system-microblazeel,
Signed-off-by: Michael Tokarev m...@tls.msk.ru
---
qemu-doc.texi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qemu-doc.texi b/qemu-doc.texi
index 8022890..185dd47 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -214,7 +214,7 @@ PCI UHCI USB controller and a virtual USB
Il 27/06/2013 20:28, Stefan Weil ha scritto:
Am 25.06.2013 18:25, schrieb Cornelia Huck:
On hosts that support ioeventfd, make use of it for host-to-guest
notifications via diagnose 500.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
hw/s390x/css.c|2 +-
Il 28/06/2013 00:25, Tomoki Sekiyama ha scritto:
+STDMETHODIMP CQGAVssProviderFactory::CreateInstance(
+IUnknown *pUnknownOuter, REFIID iid, void **ppv)
+{
+if (pUnknownOuter) {
+return CLASS_E_NOAGGREGATION;
+}
+CQGAVssProvider *pObj = new CQGAVssProvider;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/06/2013 00:58, Eric Blake ha scritto:
Using the previous patches, we're now able to timestamp the
SETUP state. Once we have this time, let the user know about it
in the schema.
Reviewed-by: Juan Quintela quint...@redhat.com Signed-off-by:
Lei Li li...@linux.vnet.ibm.com writes:
On 06/27/2013 10:22 PM, Markus Armbruster wrote:
This reverts commit 6a85e60cb994bd95d1537aafbff65816f3de4637.
Commit 51767e7 qemu-char: Add new char backend CirMemCharDriver
introduced a memory ring buffer character device driver named
memory.
Il 28/06/2013 00:56, Peter Maydell ha scritto:
On 27 June 2013 23:44, mrhi...@linux.vnet.ibm.com wrote:
arch_init.c | 29 +++--
include/migration/migration.h |2 ++
Implementation in arch_init.c but prototype in migration.h?
The function
Il 28/06/2013 00:44, mrhi...@linux.vnet.ibm.com ha scritto:
+ *
+ * This will have a terrible impact on migration performance, so until future
+ * workload information or LRU information is available, do not attempt to
use
+ * this feature except for basic testing.
+ */
+//#define
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/06/2013 01:10, Eric Blake ha scritto:
Isn't this a repeat from your earlier series v12?
Juan didn't apply all the patches because he had some issues with the
later ones.
Paolo
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
event_notifier_get_fd() is not available on windows hosts. Fix this by
moving the calls to event_notifier_get_fd() to the kvm code.
Reported-by: Stefan Weil s...@weilnetz.de
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
hw/s390x/virtio-ccw.c |6 ++
target-s390x/cpu.h|
Hi,
I am trying to debug an OS with the help of qemu. I use the log files
generated by adding the following string in the command to start the QEMU :
-d in_asm,cpu,int,exec
The problem is that when the OS enters the a loop , only a single iteration
of the loop is shown. Rest of the iterations
Il 28/06/2013 09:47, Cornelia Huck ha scritto:
event_notifier_get_fd() is not available on windows hosts. Fix this by
moving the calls to event_notifier_get_fd() to the kvm code.
Reported-by: Stefan Weil s...@weilnetz.de
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
Il 27/06/2013 20:16, Stefano Stabellini ha scritto:
Support backend option direct-io-safe. This is documented as
follows in the Xen backend specification:
* direct-io-safe
* Values: 0/1 (boolean)
* Default Value: 0
*
* The underlying storage is not affected
Am 27.06.2013 um 15:52 hat Peter Lieven geschrieben:
.has_zero_init defaults to 1 for all formats and protocols.
this is a dangerous default since this means that all
new added drivers need to manually overwrite it to 0 if
they do not ensure that a device is zero initialized
after
Thanks for your answer. I'm confused! A lot of frontends (like qemu-
launcher) ask for the qemu binary. Haven't they noticed this change? How
can one make qemu-launcher work again? Is it ok to link qemu-system-i386
to qemu?
--
You received this bug notification because you are a member of qemu-
On 28.06.2013 10:06, Kevin Wolf wrote:
Am 27.06.2013 um 15:52 hat Peter Lieven geschrieben:
.has_zero_init defaults to 1 for all formats and protocols.
this is a dangerous default since this means that all
new added drivers need to manually overwrite it to 0 if
they do not ensure that a device
Am 28.06.2013 um 10:16 hat Peter Lieven geschrieben:
On 28.06.2013 10:06, Kevin Wolf wrote:
Am 27.06.2013 um 15:52 hat Peter Lieven geschrieben:
.has_zero_init defaults to 1 for all formats and protocols.
this is a dangerous default since this means that all
new added drivers need to
Depending on the subformat, has_zero_init on VHD must behave like raw
and query the underlying storage (fixed) or like other sparse formats
that can always return 1 (dynamic, differencing).
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block/vpc.c | 25 +++--
1 file changed,
On 28.06.2013 10:20, Kevin Wolf wrote:
Am 28.06.2013 um 10:16 hat Peter Lieven geschrieben:
On 28.06.2013 10:06, Kevin Wolf wrote:
Am 27.06.2013 um 15:52 hat Peter Lieven geschrieben:
.has_zero_init defaults to 1 for all formats and protocols.
this is a dangerous default since this means
Stefano,
--On 27 June 2013 19:16:30 +0100 Stefano Stabellini
stefano.stabell...@eu.citrix.com wrote:
* Therefore this option gives the backend permission to use
* O_DIRECT, notwithstanding that bug.
Looks useful. Are you planning to do this for both emulated and pv
disks?
--
Judging from its website, qemu-launcher hasn't had a release or even a
change in its source code for over five years. It's not very surprising
that it's broken. I suggest you find a replacement that's actively
maintained and keeps up with changes in QEMU.
--
You received this bug notification
Right! I didn't check that because I assumed Ubuntu only uses maintained
projects. Sorry for not checking. After a day using console seems
fine...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Am 28.06.2013 um 10:25 hat Peter Lieven geschrieben:
On 28.06.2013 10:20, Kevin Wolf wrote:
Am 28.06.2013 um 10:16 hat Peter Lieven geschrieben:
On 28.06.2013 10:06, Kevin Wolf wrote:
Am 27.06.2013 um 15:52 hat Peter Lieven geschrieben:
.has_zero_init defaults to 1 for all formats and
On 28.06.2013 12:09, Kevin Wolf wrote:
Am 28.06.2013 um 10:25 hat Peter Lieven geschrieben:
On 28.06.2013 10:20, Kevin Wolf wrote:
Am 28.06.2013 um 10:16 hat Peter Lieven geschrieben:
On 28.06.2013 10:06, Kevin Wolf wrote:
Am 27.06.2013 um 15:52 hat Peter Lieven geschrieben:
.has_zero_init
On 28.06.2013 10:06, Kevin Wolf wrote:
Am 27.06.2013 um 15:52 hat Peter Lieven geschrieben:
.has_zero_init defaults to 1 for all formats and protocols.
this is a dangerous default since this means that all
new added drivers need to manually overwrite it to 0 if
they do not ensure that a device
24.06.2013 23:21, Ed Maste wrote:
Signed-off-by: Ed Maste ema...@freebsd.org
---
I have had this in a local tree for some time, and it is needed by the
BSD-user work that is now being proposed.
So I'm not applying this to -trivial, because it caused quite some
discussion. If nevertheless
10.06.2013 19:40, Michael Tokarev wrote:
07.06.2013 07:51, Peter Crosthwaite wrote:
[]
Id like to give it a few days to see what they say before we merge
this. Ideally we have agreement between the two source trees, so we
can continue the copy-paste based update strategy.
Do we have any
Ping?
19.06.2013 16:34, Michael Tokarev wrote:
It looks like initially there was -nographic option to turn
off display, now there's another option of the same sort,
-display none. But code in other places of qemu checks for
DT_NOGRAPHIC and does not work well with -display none.
Make
On 06/28/13 09:05, Paolo Bonzini wrote:
Il 28/06/2013 00:25, Tomoki Sekiyama ha scritto:
+STDMETHODIMP CQGAVssProviderFactory::CreateInstance(
+IUnknown *pUnknownOuter, REFIID iid, void **ppv)
+{
+if (pUnknownOuter) {
+return CLASS_E_NOAGGREGATION;
+}
+
19.06.2013 23:35, Anthony Liguori wrote:
Michael Tokarev m...@tls.msk.ru writes:
Signed-off-by: Michael Tokarev m...@tls.msk.ru
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Thank you for the review. Ok to apply it to the
trivial tree, since the change is quite simple?
Thanks,
/mjt
Il 28/06/2013 12:40, Laszlo Ersek ha scritto:
Also, this is not running in the context of qemu-ga, so I think it is
better to be more conservative and trap memory allocation failure.
In that case other new calls must assume the nothrow form too, plus
other allocation functions should be
+STDAPI DllCanUnloadNow()
+{
+return g_nComObjsInUse == 0 ? S_OK : S_FALSE;
+}
Don't you need some kind of atomic or locked read here? We could read a
stale value here. Granted, most stale values would err on the safe side
(ie. read 0 instead of ==0), but in theory the other mistake is
On Tue, Jun 25, 2013 at 01:16:38PM +0200, Laszlo Ersek wrote:
On 06/06/13 17:06, Tomoki Sekiyama wrote:
To enable VSS support in qemu-ga for Windows, header files included in
VSS SDK are required.
The VSS support is enabled by the configure option like below:
./configure
Alex Bligh writes (Re: [Qemu-devel] [PATCH v2] xen_disk: support
direct-io-safe backend option):
Stefano,
--On 27 June 2013 19:16:30 +0100 Stefano Stabellini
stefano.stabell...@eu.citrix.com wrote:
* Therefore this option gives the backend permission to use
* O_DIRECT,
.has_zero_init defaults to 1 for all formats and protocols.
this is a dangerous default since this means that all
new added drivers need to manually overwrite it to 0 if
they do not ensure that a device is zero initialized
after bdrv_create().
if a driver needs to explicitly set this value to
1
Il 28/06/2013 12:43, Daniel P. Berrange ha scritto:
On Tue, Jun 25, 2013 at 01:16:38PM +0200, Laszlo Ersek wrote:
On 06/06/13 17:06, Tomoki Sekiyama wrote:
To enable VSS support in qemu-ga for Windows, header files included in
VSS SDK are required.
The VSS support is enabled by the configure
Paolo Bonzini writes (Re: [PATCH v2] xen_disk: support direct-io-safe
backend option):
Il 27/06/2013 20:16, Stefano Stabellini ha scritto:
The original proposal for a cache backend option has been dropped
because it was believed too wide, especially considering that at the
moment the
On Fri, 28 Jun 2013, Alex Bligh wrote:
Stefano,
--On 27 June 2013 19:16:30 +0100 Stefano Stabellini
stefano.stabell...@eu.citrix.com wrote:
* Therefore this option gives the backend permission to use
* O_DIRECT, notwithstanding that bug.
Looks useful. Are you planning to
On Fri, 28 Jun 2013, Paolo Bonzini wrote:
Il 27/06/2013 20:16, Stefano Stabellini ha scritto:
Support backend option direct-io-safe. This is documented as
follows in the Xen backend specification:
* direct-io-safe
* Values: 0/1 (boolean)
* Default Value: 0
*
On Fri, Jun 28, 2013 at 12:54:04PM +0200, Paolo Bonzini wrote:
Il 28/06/2013 12:43, Daniel P. Berrange ha scritto:
On Tue, Jun 25, 2013 at 01:16:38PM +0200, Laszlo Ersek wrote:
On 06/06/13 17:06, Tomoki Sekiyama wrote:
To enable VSS support in qemu-ga for Windows, header files included in
On 06/28/13 12:43, Daniel P. Berrange wrote:
On Tue, Jun 25, 2013 at 01:16:38PM +0200, Laszlo Ersek wrote:
On 06/06/13 17:06, Tomoki Sekiyama wrote:
To enable VSS support in qemu-ga for Windows, header files included in
VSS SDK are required.
The VSS support is enabled by the configure option
Il 28/06/2013 13:01, Daniel P. Berrange ha scritto:
What is the license of the VSS SDK ? In particular is the license
compatible with QEMU to allow us to link to it from GPL code ?
Doesn't it fall under the operating system component exception?
Maybe, maybe no. I think it depends what the
On 19 June 2013 13:34, Michael Tokarev m...@tls.msk.ru wrote:
It looks like initially there was -nographic option to turn
off display, now there's another option of the same sort,
-display none. But code in other places of qemu checks for
DT_NOGRAPHIC and does not work well with -display
On 28 June 2013 11:39, Michael Tokarev m...@tls.msk.ru wrote:
19.06.2013 23:35, Anthony Liguori wrote:
Michael Tokarev m...@tls.msk.ru writes:
Signed-off-by: Michael Tokarev m...@tls.msk.ru
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Thank you for the review. Ok to apply it to the
28.06.2013 15:24, Peter Maydell wrote:
On 19 June 2013 13:34, Michael Tokarev m...@tls.msk.ru wrote:
It looks like initially there was -nographic option to turn
off display, now there's another option of the same sort,
-display none. But code in other places of qemu checks for
DT_NOGRAPHIC
On Fri, Jun 28, 2013 at 01:18:10PM +0200, Paolo Bonzini wrote:
Il 28/06/2013 13:01, Daniel P. Berrange ha scritto:
What is the license of the VSS SDK ? In particular is the license
compatible with QEMU to allow us to link to it from GPL code ?
Doesn't it fall under the operating system
On 28 June 2013 12:29, Michael Tokarev m...@tls.msk.ru wrote:
28.06.2013 15:24, Peter Maydell wrote:
...in particular I don't think -display none should
mean don't allow ctrl-c (though -nographic should
continue to have that effect), and this patch currently
introduces that behaviour change.
A common operation in instruction decoding is to take a field
from an instruction that represents a signed integer in some
arbitrary number of bits, and sign extend it into a C signed
integer type for manipulation. Provide new functions sextract32()
and sextract64() which perform this operation;
Add some simple test cases for the new sextract32
and sextract64 functions.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
tests/Makefile |2 ++
tests/test-bitops.c | 75 +++
2 files changed, 77 insertions(+)
create mode
28.06.2013 15:34, Peter Maydell wrote:
On 28 June 2013 12:29, Michael Tokarev m...@tls.msk.ru wrote:
28.06.2013 15:24, Peter Maydell wrote:
...in particular I don't think -display none should
mean don't allow ctrl-c (though -nographic should
continue to have that effect), and this patch
Am 28.06.2013 13:29, schrieb Michael Tokarev:
28.06.2013 15:24, Peter Maydell wrote:
On 19 June 2013 13:34, Michael Tokarev m...@tls.msk.ru wrote:
It looks like initially there was -nographic option to turn
off display, now there's another option of the same sort,
-display none. But code in
28.06.2013 15:45, Andreas Färber пишет:
Am 28.06.2013 13:29, schrieb Michael Tokarev:
28.06.2013 15:24, Peter Maydell wrote:
[]
...in particular I don't think -display none should
mean don't allow ctrl-c (though -nographic should
continue to have that effect), and this patch currently
On 28 June 2013 12:43, Michael Tokarev m...@tls.msk.ru wrote:
Note it is used only for stdio char device, like -serial stdio,
so if you _just_ use -display none, without -serial stdio, you
wont notice a change.
Yes, I use -display none -serial stdio.
-- PMM
Am 28.06.2013 13:27, schrieb Peter Maydell:
On 28 June 2013 11:39, Michael Tokarev m...@tls.msk.ru wrote:
19.06.2013 23:35, Anthony Liguori wrote:
Michael Tokarev m...@tls.msk.ru writes:
Signed-off-by: Michael Tokarev m...@tls.msk.ru
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Thank
There are cases where a kvm provided function is called from generic
hw code that doesn't know whether kvm is available or not. Provide
a stub file which can provide simple replacement functions for those
cases.
Signed-off-by: Alexander Graf ag...@suse.de
diff --git a/target-ppc/Makefile.objs
A common operation in instruction decoding is to take a field
from an instruction that represents a signed integer in some
arbitrary number of bits, and sign extend it into a C signed
integer type for manipulation. Provide new functions sextract32()
and sextract64() which perform this operation;
On 28 June 2013 12:50, Michael Tokarev m...@tls.msk.ru wrote:
Um. With either -nographic or -display none, there's no display
per se, and it is the display who relays keypresses and such into
guest. Without display, the guest becomes headless completely, not
only it does not have a monitor of
Am 28.06.2013 13:50, schrieb Michael Tokarev:
28.06.2013 15:45, Andreas Färber пишет:
Am 28.06.2013 13:29, schrieb Michael Tokarev:
28.06.2013 15:24, Peter Maydell wrote:
[]
...in particular I don't think -display none should
mean don't allow ctrl-c (though -nographic should
continue to
On 28.06.2013, at 13:54, Alexander Graf wrote:
There are cases where a kvm provided function is called from generic
hw code that doesn't know whether kvm is available or not. Provide
a stub file which can provide simple replacement functions for those
cases.
Signed-off-by: Alexander Graf
Am 28.06.2013 um 12:47 hat Peter Lieven geschrieben:
.has_zero_init defaults to 1 for all formats and protocols.
this is a dangerous default since this means that all
new added drivers need to manually overwrite it to 0 if
they do not ensure that a device is zero initialized
after
Il 28/06/2013 13:43, Michael Tokarev ha scritto:
All I'm saying is that I use -display none and I like that
it defaults to ctrl-c works and kills qemu and I don't
want you to break that :-)
I'm not. Code in qemu-char.c:
static bool stdio_allow_signal;
static void
Am 28.06.2013 13:50, schrieb Michael Tokarev:
28.06.2013 15:45, Andreas Färber пишет:
Am 28.06.2013 13:29, schrieb Michael Tokarev:
28.06.2013 15:24, Peter Maydell wrote:
[]
...in particular I don't think -display none should
mean don't allow ctrl-c (though -nographic should
continue to
28.06.2013 15:55, Peter Maydell wrote:
On 28 June 2013 12:50, Michael Tokarev m...@tls.msk.ru wrote:
This ctrl+c handling is only about when you explicitly redirected
some other char device to guest, such as serial port. Which don't
have much to do with display I think, hence I don't
Il 28/06/2013 14:05, Michael Tokarev ha scritto:
That's exactly why I don't think looking at -nographic here in
serial code is wrong. It should do the same regardless of
-nographic - if, say, serial is redirected to stdio, it should
always pass Ctrl+C to guest instead of killing it. So I'm
On 28 June 2013 13:05, Michael Tokarev m...@tls.msk.ru wrote:
28.06.2013 15:55, Peter Maydell wrote:
The point is that one of the things -nographic does, as well
as disabling the graphics display, is to redirect the serial
port (among other things) to stdio. That's why there's code
in the
Il 28/06/2013 14:05, Andreas Färber ha scritto:
BTW just try it out using the following to see for yourself:
$ qemu-system-ppc -nographic
should get you to an interactive OpenBIOS prompt. Same for sparc.
This involves communicating to firmware that we are in -nographic mode,
which then
Il 28/06/2013 13:56, Alexander Graf ha scritto:
On 28.06.2013, at 13:54, Alexander Graf wrote:
There are cases where a kvm provided function is called from generic
hw code that doesn't know whether kvm is available or not. Provide
a stub file which can provide simple replacement functions
From: Mian M. Hamayun m.hama...@virtualopensystems.com
Signed-off-by: Mian M. Hamayun m.hama...@virtualopensystems.com
---
configure |3 +-
default-configs/aarch64-softmmu.mak | 83 +++
2 files changed, 85 insertions(+), 1
From: Mian M. Hamayun m.hama...@virtualopensystems.com
The vexpress model for A57 is based on the A15 machine model with a few
changes in the daughterboard initialization (using a subset of A15
functionality). The A57 daughterboard init also shares the A15MPCore
private memory region with A15
From: Mian M. Hamayun m.hama...@virtualopensystems.com
Signed-off-by: Mian M. Hamayun m.hama...@virtualopensystems.com
---
linux-headers/asm-arm64/kvm.h | 168
linux-headers/asm-arm64/kvm_para.h |1 +
2 files changed, 169 insertions(+)
create mode
From: Mian M. Hamayun m.hama...@virtualopensystems.com
This version supports booting of a single Aarch64 CPU by setting appropriate
registers. The bootloader includes placehoders for Board-ID that are used to
implementing uniform indexing across different bootloaders.
The same macro names are
Il 28/06/2013 13:30, Daniel P. Berrange ha scritto:
Does the VSS SDK actually include the .dll library that qemu-ga would
be linking aginst, or is the .dll part of base windows install, and
VSS SDK merely includes the header files needed for compilation ?
Only the headers, the IDL
Hi,
I try to develop a CAN device on QEMU. And I found pci-serial is similar to
CAN.
Untill now, I have some questions about how to use pci-serial on QEMU.
Actually, QEMU use isa-serial as a default serial device. So I try to use
isa-serial firstly.
Some useful information we can get from
From: Alexander Spyridakis a.spyrida...@virtualopensystems.com
AArch64 uses a cpu-release-addr memory location (defined in the dts) as
a way to inform secondary CPUs where to jump to and enter their holding
pen. Inject a very simple bootloader that polls this memory location,
until the primary
This patch series implements KVM support in QEMU for the ARMv8 Cortex
A57 CPU.
It depends on the previously submitted AArch64 Preparation Patchset V4,
and uses
as a base, the existing Versatile Express machine model and the already
available KVM in-kernel GIC support.
As a reference, KVM Tool
From: Mian M. Hamayun m.hama...@virtualopensystems.com
The init function tries to initialize with Foundation models first and on
failure retries initializing on Fast Models.
Get and Put Registers deal with the basic state of Aarch64 CPUs for the moment.
Signed-off-by: Mian M. Hamayun
On 28.06.2013, at 14:11, Mian M. Hamayun wrote:
From: Mian M. Hamayun m.hama...@virtualopensystems.com
The init function tries to initialize with Foundation models first and on
failure retries initializing on Fast Models.
Get and Put Registers deal with the basic state of Aarch64 CPUs
On 28 June 2013 13:20, Mian M. Hamayun m.hama...@virtualopensystems.com wrote:
This patch series implements KVM support in QEMU for the ARMv8 Cortex
A57 CPU.
It depends on the previously submitted AArch64 Preparation Patchset V4,
and uses
as a base, the existing Versatile Express machine
Hi,
Am 28.06.2013 14:19, schrieb Yang Jin:
I try to develop a CAN device on QEMU. And I found pci-serial is similar
to CAN.
Untill now, I have some questions about how to use pci-serial on QEMU.
Actually, QEMU use isa-serial as a default serial device. So I try to
use isa-serial firstly.
The drqbmp field of struct soc_dma_s is a uint64_t; however several
places in the code attempt to set bits in it using (1 drq),
which will fail if drq is large enough that the 1 bit gets shifted
off the top of a 32 bit integer. Change these to (1ULL drq) so
that the promotion to 64 bit happens
On 28 June 2013 06:34, Michael Tokarev m...@tls.msk.ru wrote:
24.06.2013 23:21, Ed Maste wrote:
Signed-off-by: Ed Maste ema...@freebsd.org
---
I have had this in a local tree for some time, and it is needed by the
BSD-user work that is now being proposed.
So I'm not applying this to
Il 28/06/2013 14:54, Ed Maste ha scritto:
On 28 June 2013 06:34, Michael Tokarev m...@tls.msk.ru wrote:
24.06.2013 23:21, Ed Maste wrote:
Signed-off-by: Ed Maste ema...@freebsd.org
---
I have had this in a local tree for some time, and it is needed by the
BSD-user work that is now being
Am 28.06.2013 14:44, schrieb Peter Maydell:
On 28 June 2013 13:20, Mian M. Hamayun m.hama...@virtualopensystems.com
wrote:
This patch series implements KVM support in QEMU for the ARMv8 Cortex
A57 CPU.
It depends on the previously submitted AArch64 Preparation Patchset V4,
and uses
as a
On 28 June 2013 14:03, Paolo Bonzini pbonz...@redhat.com wrote:
Il 28/06/2013 14:54, Ed Maste ha scritto:
An objection seemed to be that it is not really needed yet, but as
pointed out by Peter this isn't really the case. This patch brings us
(FreeBSD) in line with per-thread data semantics
On 28 June 2013 14:04, Andreas Färber afaer...@suse.de wrote:
I had been looking into that tree myself, and apart from John's
Linux'ish ARM: prefixes rather than our usual target-arm: (part of
which you forgot to fix before sending a PULL), I am really opposed to
copying A15MPCore_priv for
On 06/27/2013 07:02 PM, Eric Blake wrote:
On 06/25/2013 07:35 PM, mrhi...@linux.vnet.ibm.com wrote:
From: Michael R. Hines mrhi...@us.ibm.com
This exposes throughput (in megabits/sec) through QMP.
Reviewed-by: Juan Quintela quint...@redhat.com
Reviewed-by: Paolo Bonzini pbonz...@redhat.com
On 06/27/2013 06:58 PM, Eric Blake wrote:
On 06/25/2013 07:35 PM, mrhi...@linux.vnet.ibm.com wrote:
From: Michael R. Hines mrhi...@us.ibm.com
Using the previous patches, we're now able to timestamp the SETUP
state. Once we have this time, let the user know about it in the
schema.
Reviewed-by:
On 06/28/2013 03:15 AM, Paolo Bonzini wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/06/2013 00:58, Eric Blake ha scritto:
Using the previous patches, we're now able to timestamp the
SETUP state. Once we have this time, let the user know about it
in the schema.
Reviewed-by: Juan
On 06/27/2013 07:09 PM, Eric Blake wrote:
On 06/27/2013 04:44 PM, mrhi...@linux.vnet.ibm.com wrote:
From: Michael R. Hines mrhi...@us.ibm.com
As requested, the protocol now includes memory unpinning support.
This has been implemented in a non-optimized manner, in such a way
that one could
ping
http://patchwork.ozlabs.org/patch/251250/
http://patchwork.ozlabs.org/patch/251254/
http://patchwork.ozlabs.org/patch/251253/
http://patchwork.ozlabs.org/patch/251251/
http://patchwork.ozlabs.org/patch/251252/
http://patchwork.ozlabs.org/patch/251249/
On 14/06/13 08:30, Leon Alrae wrote:
The functions cpu_clone_regs() and cpu_set_tls() are not purely CPU
related -- they are specific to the TLS ABI for a a particular OS.
Move them into the linux-user/ tree where they belong.
target-lm32 had entirely unused implementations, since it has no
linux-user target; just drop them.
On 06/27/2013 07:16 PM, Peter Maydell wrote:
On 27 June 2013 23:44, mrhi...@linux.vnet.ibm.com wrote:
+if test $rdma != no ; then
+ cat $TMPC EOF
+#include rdma/rdma_cma.h
+int main(void) { return 0; }
+EOF
+ rdma_libs=-lrdmacm -libverbs
+ if compile_prog -Werror $rdma_libs ; then
Do you
A transition from CPUFooState to FooCPU can be considered safe,
just like FooCPU::env access in the opposite direction.
The only benefit of the FOO_CPU() casts would be protection against
bogus CPUFooState pointers, but then surrounding code would likely
break, too.
This should slightly improve
On 28 June 2013 14:23, Michael R. Hines mrhi...@linux.vnet.ibm.com wrote:
I assume from the PACKED annotations (do we really need both,
incidentally) that this is shared with either the guest or
with another instance of QEMU. Are there definitely no
endianness issues to deal with here?
I
On 06/28/2013 01:15 AM, Paolo Bonzini wrote:
Il 28/06/2013 00:58, Eric Blake ha scritto:
Using the previous patches, we're now able to timestamp the
SETUP state. Once we have this time, let the user know about it
in the schema.
Reviewed-by: Juan Quintela quint...@redhat.com Signed-off-by:
On 06/27/2013 08:22 AM, Markus Armbruster wrote:
Commit 1da48c6 called the new member memory after commit 3949e59
standardized ringbuf. Rename for consistency.
However, member name memory is visible in QMP since 1.5. It's
undocumented just like the driver name. Keep it working anyway.
On 2013-06-25 13:13, Paolo Bonzini wrote:
Once address_space_translate will only be protected by RCU, the returned
MemoryRegion can disappear as soon as the RCU read-side critical
section ends. Avoid this by adding a reference to the region, and
dropping it in the caller of
On 06/27/2013 08:25 PM, Wenchao Xia wrote:
+readline_add_completion(mon-rs, file);
}
}
closedir(ffs);
Oops, I started reviewing that before noticing you posted a v3. At any
rate, my review of v2 still stands on this patch. Meanwhile, I just
barely
Make sure we use the correct TARGET/PRI macros in the debug statements.
Signed-off-by: Mark Cave-Ayland mark.cave-ayl...@ilande.co.uk
CC: Kevin Wolf kw...@redhat.com
---
hw/ide/cmd646.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/ide/cmd646.c b/hw/ide/cmd646.c
On 06/25/2013 09:41 AM, Michael S. Tsirkin wrote:
From: Amos Kong ak...@redhat.com
Currently macvtap based macvlan device is working in promiscuous
mode, we want to implement mac-programming over macvtap through
Libvirt for better performance.
Michael S. Tsirkin: tweaked to enable events
1 - 100 of 294 matches
Mail list logo
