Check that "$QEMU -M none -cpu FOO" starts QEMU without error
Signed-off-by: Igor Mammedov
---
v2:
- rename file to machine-none-test.c (Thomas Huth )
- use qtest_startf()/instead of qtest_start() (Thomas Huth )
---
tests/Makefile.include| 2 ++
tests/machine-none-test.c | 68 ++
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
thest would ensure that null-mchine usecase still works.
Signed-off-by: Igor Ma
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
v3:
- use qtest_startf() instead of qtest_start()
- rename tests/machine-none.c to tests/machine-none-test.c
- introduce first CPU_RESOLVING_TYPE for all targets and
only then use it parse_cpu_model()
- stop abusing mc->default_cpu_type as resolving cpu type,
move cpu_parse_cpu_m
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
use cpu_create() instead of being removed cpu_generic_init()
Signed-off-by: Igor Mammedov
---
CC: Chris Wulff
CC: Marek Vasut
---
hw/nios2/10m50_devboard.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/nios2/10m50_devboard.c b/hw/nios2/10m50_devboard.c
index e4007f6..4
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
PC:
target cpu can't be instantiated with -M none -cpu
Add FIXME note in test, so microblaze maintainers
could fix it in future and add proper error checking
in cpu_model resolve
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
TODO:
make nios2_cpu_c
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
With all targets defining CPU_RESOLVING_TYPE, refactor
cpu_parse_cpu_model(type, cpu_model) to parse_cpu_model(cpu_model)
so that callers won't have to know internal resolving cpu
type. Place it in exec.c so it could be called from both
target independed vl.c and *-user/main.c.
That allows us to s
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
cpu_init(cpu_model) were replaced by cpu_create(cpu_type) so
no users are left, remove it.
Signed-off-by: Igor Mammedov
---
CC: Richard Henderson (maintainer:Alpha)
CC: Peter Maydell
CC: "Edgar E. Iglesias"
CC: Eduardo Habkost
CC: Michael Walle
CC: Laurent Vivier
CC: Aurelien Jarno
CC: Yon
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
PS:
sparc cpu model nam
There aren't any users of the helper left, remove it.
Signed-off-by: Igor Mammedov
---
CC: Richard Henderson
CC: "Emilio G. Cota"
CC: Paolo Bonzini
CC: Eduardo Habkost
CC: "Alex Bennée"
CC: "Philippe Mathieu-Daudé"
---
qom/cpu.c | 17 ++---
1 file changed, 2 insertions(+), 15 d
On Thu, Jan 18, 2018 at 2:51 PM, Peter Maydell wrote:
> On 18 January 2018 at 02:01, Eduardo Habkost wrote:
>> The following changes since commit 8e5dc9ba49743b46d955ec7dacb04e42ae7ada7c:
>>
>> Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20180116' into
>> staging (2018-01-16 17:36:
Function cpu_handle_interrupt calls cc->cpu_exec_interrupt to process
pending hardware interrupts. Under the hood cpu_exec_interrupt uses
cpu->exception_index to pass information to the internal function which
is usually common for exception and interrupt processing.
But this value is not reset aft
Accidentally sent draft version of patches to the mailing list.
Please consider this one as the correct one.
This set of patches includex fixes from Alex Bennée for fixing
BQL and replay locks after inventing the MTTCG. It also includes some
additional replay patches that makes this set of fixes w
From: Pavel Dovgalyuk
This patch enables making snapshots with blkreplay used in
block devices.
This function is required to make bdrv_snapshot_goto without
calling .bdrv_open which is not implemented.
Signed-off-by: Pavel Dovgalyuk
---
block/blkreplay.c |8
1 file changed, 8 inse
This patch fixes assignment to internal events_enabled variable.
Now it is set only in record/replay mode. This affects the behavior
of the external functions that check this flag.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
---
replay/replay-events.c |8 +---
1 file changed,
Asynchronous events saved at checkpoints may invoke
callbacks when processed. These callbacks may also generate/read
new events (e.g. clock reads). Therefore event processing flag must be
reset before callback invocation.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
---
replay/replay-
From: Pavel Dovgalyuk
This patch allows using '-snapshot' behavior in record/replay mode.
blkreplay layer creates temporary overlays on top of underlaying
disk images. It is needed, because creating an overlay over blkreplay
breaks the determinism.
This patch creates similar temporary overlay (wh
From: Pavel Dovgalyuk
This patch disables setting '-snapshot' option on by default
in record/replay mode. This is needed for creating vmstates in record
and replay modes.
Signed-off-by: Pavel Dovgalyuk
---
vl.c |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/vl.c
This patch does not allows saving/loading vmstate when
replay events queue is not empty. There is no reliable
way to save events queue, because it describes internal
coroutine state. Therefore saving and loading operations
should be deferred to another record/replay step.
Signed-off-by: Pavel Dovg
From: Alex Bennée
The powerctl code is run in the context of the vCPU changing power
state. It does not need the BQL to protect its changes.
Signed-off-by: Alex Bennée
---
target/arm/arm-powerctl.c |8
1 file changed, 8 deletions(-)
diff --git a/target/arm/arm-powerctl.c b/target
From: Pavel Dovgalyuk
This patch adds description of the replay log file format
into the docs/replay.txt.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
---
docs/replay.txt | 69 +++
1 file changed, 69 insertions(+)
diff --git a/d
This patch adds saving/restoring of the host clock field 'last'.
It is used in host clock calculation and therefore clock may
become incorrect when using restored vmstate.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
---
include/qemu/timer.h | 14 ++
replay/replay-in
From: Alex Bennée
Now instead of using the replay_lock to guard the output of the log we
now use it to protect the whole execution section. This replaces what
the BQL used to do when it was held during TCG execution.
We also introduce some rules for locking order - mainly that you
cannot take th
BQL now is used only for waiting for IO events.
This patch also removes lock/unlock from hax module.
Signed-off-by: Pavel Dovgalyuk
---
target/i386/hax-all.c |2 --
1 file changed, 2 deletions(-)
diff --git a/target/i386/hax-all.c b/target/i386/hax-all.c
index 934ec4a..54b1fc7 100644
--- a/
From: Alex Bennée
The replay_mutex_lock/unlock/locked functions are now going to be used
for ensuring lock-step behaviour between the two threads. Make them
public API functions and also provide stubs for non-QEMU builds on
common paths.
Signed-off-by: Alex Bennée
Tested-by: Pavel Dovgalyuk
--
From: Alex Bennée
We only really need to grab the lock for initial setup (so we don't
race with the thread-spawning thread). After that we can drop the lock
for the whole main loop and only grab it for waiting for IO events.
There is a slight wrinkle for the round-robin TCG thread as we also
exp
BQL now is used only for waiting for IO events.
This patch also removes lock/unlock from kvm module.
Signed-off-by: Pavel Dovgalyuk
---
accel/kvm/kvm-all.c |2 --
1 file changed, 2 deletions(-)
diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
index 9628512..d708c7f 100644
--- a/accel/
From: Alex Bennée
This time commit 802f045a5f61b781df55e4492d896b4d20503ba7 broke the
replay file format. Also add a comment about this to
replay-internal.h.
Signed-off-by: Alex Bennée
Reviewed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
---
replay/replay-internal.h |2 +-
replay/rep
This patch adds a flag which denies recursive call of replay_checkpoint
function. Checkpoints may be accompanied by the hardware events. When event
is processed, virtual device may invoke timer modification functions that
also invoke the checkpoint function. This leads to infinite loop.
Signed-off
From: Alex Bennée
This is modelled after the iothread mutex lock. We keep a TLS flag to
indicate when that thread has acquired the lock and assert we don't
double-lock or release when we shouldn't have.
Signed-off-by: Alex Bennée
Tested-by: Pavel Dovgalyuk
---
replay/replay-internal.c | 11
Replay mutex is held by vCPU thread and destroy function is called
from atexit of the main thread. Therefore we cannot destroy it safely.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
---
replay/replay.c |1 -
1 file changed, 1 deletion(-)
diff --git a/replay/replay.c b/replay/rep
Virtual clock is warped from iothread and vcpu thread. When the hardware
events associated with warp checkpoint, then interrupt delivering may be
non-deterministic if checkpoint is processed in different threads in record
and replay.
This patch disables event processing for clock warp checkpoint an
This patch adds error reporting when fwrite cannot completely
save the buffer to the file.
Signed-off-by: Pavel Dovgalyuk
--
v3: also check putc() return value
---
replay/replay-internal.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/replay/replay-in
This patch fixes saving and loading the snapshots in the replay mode.
It is required for the snapshots created in the moment when the header
of the asynchronous event is read. This information was not saved in
the snapshot. After loading the vmstate replay continued with the file offset
passed the
From: Alex Bennée
This script is a debugging tool for looking through the contents of a
replay log file. It is incomplete but should fail gracefully at events
it doesn't understand.
It currently understands two different log formats as the audio
record/replay support was merged during since MTTC
In record/replay mode bdrv queue is controlled by replay mechanism.
It does not allow stopping the vm, saving or loading the snapshots
when bdrv queue is not empty. Therefore draining and flushing is unnecessary
(and may cause deadlocks in replay mode).
This patch disables bdrv_drain_all and bdrv_f
On Tue, Jan 23, 2018 at 09:08:02AM +0100, Igor Mammedov wrote:
> it will be used for providing to cpu name resolving class for
> parsing cpu model for system and user emulation code.
>
> Along with change add target to null-machine test, so
> that when switch to CPU_RESOLVING_TYPE happens,
> thest
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
thest would ensure that null-mchine usecase still works.
Signed-off-by: Igor Ma
it will be used for providing to cpu name resolving class for
parsing cpu model for system and user emulation code.
Along with change add target to null-machine test, so
that when switch to CPU_RESOLVING_TYPE happens,
test would ensure that null-mchine usecase still works.
Signed-off-by: Igor Mam
On 01/23/2018 09:40 AM, Christian Ehrhardt wrote:
> On Thu, Jan 18, 2018 at 2:51 PM, Peter Maydell
> wrote:
>> On 18 January 2018 at 02:01, Eduardo Habkost wrote:
>>> The following changes since commit 8e5dc9ba49743b46d955ec7dacb04e42ae7ada7c:
>>>
>>> Merge remote-tracking branch 'remotes/rt
On 2018年01月23日 04:04, Michael S. Tsirkin wrote:
On Mon, Jan 22, 2018 at 12:17:51PM +, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
These patches implement the virtio-vhost-user device design that I have
de
On Fri, 2018-01-19 at 15:34 +0100, Andrea Bolognani wrote:
> > > This won't solve the libvirt problem we were discussing, because it
> > > needs an existing instance of the object. libvirt wants to know the
> > > machine properties *without* instantiating an instance.
> >
> > My patch works with
On 22 January 2018 at 13:38, Peter Maydell wrote:
> On 22 January 2018 at 12:38, Dr. David Alan Gilbert
> wrote:
>> It's probably better to remove the whole set of 6, then we can come
>> back to it later rather than leaving something half-implemented in
>> there.
>
> OK. I'm currently running a
On Mon, Jan 22, 2018 at 10:04:18PM +0200, Michael S. Tsirkin wrote:
> On Mon, Jan 22, 2018 at 12:17:51PM +, Stefan Hajnoczi wrote:
> > On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
> > > On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
> > > > These patches implement the virtio-vhost-
On 22 January 2018 at 03:41, Richard Henderson
wrote:
> This has some improvements to the patch set posted on Dec 28.
>
> * Change cpu init as requested by Igor Mammedov.
> * Add SMP support
> * Add firmware image
> * Implement qemu-specific pause and system reset insns.
>
>
> r~
>
>
> The
On Tue, 23 Jan 2018 10:59:39 +0100
Christian Borntraeger wrote:
> On 01/23/2018 09:40 AM, Christian Ehrhardt wrote:
> > On Thu, Jan 18, 2018 at 2:51 PM, Peter Maydell
> > wrote:
> >> On 18 January 2018 at 02:01, Eduardo Habkost wrote:
> >>> The following changes since commit
> >>> 8e5dc9b
On Jan 23 2018, Laurent Vivier wrote:
> Please fix style problem reported by patchew
> (or ./scripts/checkpatch.pl)
This was mostly copy-pasted from surrounding code. :-)
>> @@ -8342,6 +8359,22 @@ abi_long do_syscall(void *cpu_env, int num, abi_long
>> arg1,
>> }
>> break;
>>
On Jan 23 2018, Laurent Vivier wrote:
> And, please, test it (build/run).
This was tested by bootstrapping openSUSE Factory for RISC-V.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something complet
On 22/1/2018 11:47 PM, Eric Blake wrote:
On 01/19/2018 06:50 AM, Anton Nefedov wrote:
Signed-off-by: Anton Nefedov
Reviewed-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Alberto Garcia
---
qapi/block-core.json | 29 +++--
include/block/accounting.h | 1 +
On Tue, Jan 23, 2018 at 10:59 AM, Christian Borntraeger
wrote:
>
>
> On 01/23/2018 09:40 AM, Christian Ehrhardt wrote:
>> On Thu, Jan 18, 2018 at 2:51 PM, Peter Maydell
>> wrote:
>>> On 18 January 2018 at 02:01, Eduardo Habkost wrote:
The following changes since commit
8e5dc9ba49743b
On 22/1/2018 11:48 PM, Eric Blake wrote:
On 01/19/2018 06:50 AM, Anton Nefedov wrote:
Signed-off-by: Anton Nefedov
---
hw/ide/core.c | 13 +
1 file changed, 13 insertions(+)
@@ -460,10 +468,15 @@ static void ide_issue_trim_cb(void *opaque, int ret)
}
On 01/22/2018 08:17 PM, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
Probably not for the following cases:
1) kick/call
I disagree here because kick/call is actually very efficient!
VM1's irqfd is the ioeventf
On Tue, 23 Jan 2018 11:34:18 +0100
Christian Ehrhardt wrote:
> On Tue, Jan 23, 2018 at 10:59 AM, Christian Borntraeger
> wrote:
> >
> >
> > On 01/23/2018 09:40 AM, Christian Ehrhardt wrote:
> >> On Thu, Jan 18, 2018 at 2:51 PM, Peter Maydell
> >> wrote:
> >>> On 18 January 2018 at 02:01, E
Le 23/01/2018 à 11:26, Andreas Schwab a écrit :
> On Jan 23 2018, Laurent Vivier wrote:
>
>> And, please, test it (build/run).
>
> This was tested by bootstrapping openSUSE Factory for RISC-V.
I have no doubt on this part, but you should test the "#else" part too,
by, for instance, undefining "
This is needed for new architectures like RISC-V which do not provide any
other rename-like syscall.
Signed-off-by: Andreas Schwab
---
linux-user/syscall.c | 34 ++
1 file changed, 34 insertions(+)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 5e
On Mon, Jan 22, 2018 at 07:09:06PM +0800, Wei Wang wrote:
> On 01/19/2018 09:06 PM, Stefan Hajnoczi wrote:
> Thanks for the quick implementation. Not sure if the following issues could
> be solved with this approach:
> - After we boot the slave VM, if we don't run the virtio-vhost-user driver
> (i
On Mon, Jan 22, 2018 at 12:41 PM, BALATON Zoltan wrote:
> Hello,
>
> On Thu, 18 Jan 2018, bzt bzt wrote:
>
>> Since you still haven't merged Alistair's patch, I decided to include it
>> in
>> my own.
>>
>
> Which patch exactly are you referring to?
The one I linked earlier, which also added CPU
On Tue, Jan 23, 2018 at 09:08:13AM +0100, Igor Mammedov wrote:
> it will be used for providing to cpu name resolving class for
> parsing cpu model for system and user emulation code.
>
> Along with change add target to null-machine test, so
> that when switch to CPU_RESOLVING_TYPE happens,
> test
On Tue, Jan 23, 2018 at 09:08:23AM +0100, Igor Mammedov wrote:
> cpu_init(cpu_model) were replaced by cpu_create(cpu_type) so
> no users are left, remove it.
>
> Signed-off-by: Igor Mammedov
ppc parts
Acked-by: David Gibson
> ---
> CC: Richard Henderson (maintainer:Alpha)
> CC: Peter Maydell
On 23 January 2018 at 10:34, Christian Ehrhardt
wrote:
> Also adding Suraj for a statement in this regard about his "[QEMU-PPC]
> [PATCH V5 0/7] target/ppc: Rework spapr_caps" series which I think is
> the PPC version of all of this right?
> Not sure who to add for Arm :-/
AIUI for Arm no QEMU ch
Le 23/01/2018 à 11:53, Andreas Schwab a écrit :
> This is needed for new architectures like RISC-V which do not provide any
> other rename-like syscall.
>
> Signed-off-by: Andreas Schwab
> ---
> linux-user/syscall.c | 34 ++
> 1 file changed, 34 insertions(+)
>
>
On 23 January 2018 at 11:13, bzt bzt wrote:
> There's a huge misunderstanding here. I have a working qemu for about half a
> year now, and I don't need it merged. It's not my goal to submit a patch to
> qemu in any way, I just did that because I had modified an Open Source
> software and wanted to
On Tue, Jan 23, 2018 at 11:08:31AM +0100, Andrea Bolognani wrote:
> On Fri, 2018-01-19 at 15:34 +0100, Andrea Bolognani wrote:
> > > > This won't solve the libvirt problem we were discussing, because it
> > > > needs an existing instance of the object. libvirt wants to know the
> > > > machine pro
I am working on creating a snapshot for ARM based VM running on A7. We don't
use disk images, so to save the snapshot I am passing "-drive if=none,
format=qcow2, file=/home/sridhar/qemu_disk_images/dummy.qcow2" as dummy disk to
save the snapshot.
Then from qemu monitor, I run the "savevm" comman
On 22/1/2018 11:55 PM, Eric Blake wrote:
On 01/19/2018 06:50 AM, Anton Nefedov wrote:
A block driver can provide a callback to report driver-specific
statistics.
file-posix driver now reports discard statistics
Signed-off-by: Anton Nefedov
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
+
From: Keno Fischer
# Background
I was investigating spurious non-deterministic EINTR returns from
various 9p file system operations in a Linux guest served from the
qemu 9p server.
## EINTR, ERESTARTSYS and the linux kernel
When a signal arrives that the Linux kernel needs to deliver to user-
Richard Henderson writes:
> Signed-off-by: Richard Henderson
Reviewed-by: Alex Bennée
> ---
> target/arm/cpu.h | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/target/arm/cpu.h b/target/arm/cpu.h
> index 1854fe51a8..3f4f6b6144 100644
> --- a/target/arm/cpu.h
> +++ b/ta
Hi,
On Mon, Jan 22, 2018 at 1:12 PM, Peter Maydell
wrote:
> On 18 January 2018 at 21:39, bzt bzt wrote:
> > Dear All,
> >
> > Since you still haven't merged Alistair's patch, I decided to include it
> in
> > my own.
> > I've shrinked the number of modified files to two, that's the bare
> minimu
On Mon, Jan 22, 2018 at 11:54:41AM +0800, Jason Wang wrote:
> On 2018年01月20日 01:20, Stefan Hajnoczi wrote:
> > > I don't propose any new idea. I just want to know what's the advantage of
> > > vhost-pci over zerocopy. Both needs one time of copy, the difference is
> > > the
> > > vhost-pci did it
Peter Maydell writes:
> On 18 January 2018 at 14:59, Philippe Mathieu-Daudé wrote:
>> My comment was for a previous line:
>>
>> uint64_t frac : 64;
>>
>> I don't have enough compiler knowledge to be sure how this bitfield is
>> interpreted by the compiler. I understood the standard as bitfi
On Tue, 2018-01-23 at 22:20 +1100, David Gibson wrote:
> > David, I know you're busy with linux.conf.au, but it would be
> > really helpful if you could carve out five minutes to look over
> > Alexey's proposal again, with my reply above in mind, and let us
> > know whether it looks a reasonable de
On Tue, Jan 23, 2018 at 12:22 PM, Peter Maydell
wrote:
> On 23 January 2018 at 11:13, bzt bzt wrote:
> > There's a huge misunderstanding here. I have a working qemu for about
> half a
> > year now, and I don't need it merged. It's not my goal to submit a patch
> to
> > qemu in any way, I just di
On Tue, Jan 23, 2018 at 01:05:28AM -0200, jos...@linux.vnet.ibm.com wrote:
> Hello people!
>
> I'm not able to boot any guest that sets a virtio block device like:
> (branch master)
>
> [PPC64]
> qemu-system-ppc64 -cpu POWER8 -nographic -vga none -m 4G -M
> pseries,accel=kvm,kvm-type=PR -drive f
hvf.c and vmx.h contain code from hvdos.c that is released as public domain:
from hvdos github: https://github.com/mist64/hvdos
"License
See LICENSE.txt (2-clause-BSD).
In order to simplify use of this code as a template, you can consider any parts
from "hvdos.c" and "interface.h" as being in
Moving it to a new file and add the BSD license there.
Signed-off-by: Izik Eidus
---
target/i386/hvf/ept_fault.h | 70 +
target/i386/hvf/hvf.c | 38 +---
2 files changed, 71 insertions(+), 37 deletions(-)
create mode 100644 t
The following 2 patch's add a missing attributions to the hvf code
Yeah, the problem looks like in virtio-pci-net. This is the output when
running in a Power 9
host:
sudo ./qemu-system-ppc64 -nographic -vga none -m 4G -M pseries,accel=kvm
-netdev type=user,id=net0 -device virtio-net-pci,netdev=net0
SLOF **
On Tue, Jan 23, 2018 at 01:03:39PM +0100, Andrea Bolognani wrote:
> On Tue, 2018-01-23 at 22:20 +1100, David Gibson wrote:
> > > David, I know you're busy with linux.conf.au, but it would be
> > > really helpful if you could carve out five minutes to look over
> > > Alexey's proposal again, with my
With a gdb attached I got the following backtrace:
Program received signal SIGABRT, Aborted.
0x75f5eff0 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x75f5eff0 in raise () at /lib64/libc.so.6
#1 0x75f6136c in abort () at /lib64/libc.so.6
#2 0x1009e704 in kvm_m
On 01/23/2018 07:12 PM, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 07:09:06PM +0800, Wei Wang wrote:
On 01/19/2018 09:06 PM, Stefan Hajnoczi wrote:
- Suppose in the future there is also a kernel virtio-vhost-user driver as
other PCI devices, can we unbind the kernel driver first, and the
On 22 January 2018 at 11:26, Thomas Huth wrote:
> The following changes since commit b384cd95eb9c6f73ad84ed1bb0717a26e29cc78f:
>
> Merge remote-tracking branch
> 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2018-01-19
> 16:35:25 +)
>
> are available in the git repository
This reverts commit 4fe6d78b2e241f41208dfb07605aace4becfc747.
As reported
http://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg05457.html
The referred commit is causing regression issues in virtio.
Signed-off-by: Jose Ricardo Ziviani
Reported-by: Anton Blanchard
---
accel/kvm/kvm-all.c
missed in 60765b6ceeb4.
Thread 1 "qemu-system-aarch64" received signal SIGSEGV, Segmentation fault.
address_space_init (as=0x0, root=0x5726e410,
name=name@entry=0x55e3f0a7 "sdhci-dma") at memory.c:3050
3050 as->root = root;
(gdb) bt
#0 address_space_init (as=0x0, root=0x55
On Tue, 2018-01-23 at 23:49 +1100, David Gibson wrote:
> It's also occurred to me that making a spapr specific approach to this
> might not be quite as horrible as I initially thought. The
> capabilities table is global (and immutable) so coding up a
> "get-spapr-caps" qapi entry point which encod
1 - 100 of 292 matches
Mail list logo
