On Tue, Jul 15, 2014 at 9:03 AM, Amit Shah wrote:
> On (Sun) 13 Jul 2014 [16:28:56], Andrey Korolyov wrote:
>> Hello,
>>
>> the issue is not specific to the iothread code because generic
>> virtio-blk also hangs up:
>
> Do you know which version works well? If you could bisect, that'll
> help a l
Cc: Eric Blake
Signed-off-by: Liu Yuan
---
qapi/block-core.json | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index e378653..22491bc 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -1384,6 +1384
This patch adds single read pattern to quorum driver and quorum vote is default
pattern.
For now we do a quorum vote on all the reads, it is designed for unreliable
underlying storage such as non-redundant NFS to make sure data integrity at the
cost of the read performance.
For some use cases as
v3:
- separate patch into two, one for quorum and one for qapi for easier review
- add enumeration for quorum read pattern
- remove unrelated blank line fix from this patch set
v2:
- rename single as 'fifo'
- rename read_all_children as read_quorum_children
- fix quorum_aio_finalize() for fi
On Mon, 14 Jul 2014 22:29:50 +0200
Paolo Bonzini wrote:
> Il 14/07/2014 05:17, Alexey Kardashevskiy ha scritto:
> >> > No, you should politely bother them again.
> >
> > That does not seem helping though :-/
>
> Sorry. :)
>
> Well, patch 1 is the same as v6 and for the others Cornelia and Alex
On (Sun) 13 Jul 2014 [16:28:56], Andrey Korolyov wrote:
> Hello,
>
> the issue is not specific to the iothread code because generic
> virtio-blk also hangs up:
Do you know which version works well? If you could bisect, that'll
help a lot.
Thanks,
Amit
On (Mon) 14 Jul 2014 [19:14:43], John Snow wrote:
> If a negative integer is used for the max_bytes parameter, QEMU currently
> calls abort() and leaves behind a core dump. This patch adds a simple
> error message to make the reason for the termination clearer.
>
> Signed-off-by: John Snow
Revie
On 07/14/2014 10:13 PM, Liu Yuan wrote:
>>> +'*read-pattern': 'str' } }
>>
>> Raw strings that encode a finite set of values are bad for type-safety.
>> Please add an enum:
>>
>> { 'enum': 'QuorumReadPattern', 'data': [ 'quorum', 'fifo' ] }
>>
>> then use '*read-pattern': 'QuorumReadP
On Mon, Jul 14, 2014 at 09:33:59PM -0600, Eric Blake wrote:
> On 07/14/2014 09:19 PM, Liu Yuan wrote:
> > This patch adds single read pattern to quorum driver and quorum vote is
> > default
> > pattern.
> >
>
> > This patch generalize the above 2 nodes case in the N nodes. That is,
> >
> > vm -
On 07/14/2014 09:19 PM, Liu Yuan wrote:
> This patch adds single read pattern to quorum driver and quorum vote is
> default
> pattern.
>
> This patch generalize the above 2 nodes case in the N nodes. That is,
>
> vm -> write to all the N nodes, read just one of them. If single read fails,
> we
+tcg_gen_addi_tl(cpu_gpr_d[r1], cpu_gpr_d[r1], const4);
Are you planning to come back to implement V and AV bits later?
Yes. I will do that in the next version of this patchset.
+case OPC1_16_SRC_MOV_A:
+/* load const4 again unsigned */
+const4 = MASK_OP_SRC_CONS
This patch adds single read pattern to quorum driver and quorum vote is default
pattern.
For now we do a quorum vote on all the reads, it is designed for unreliable
underlying storage such as non-redundant NFS to make sure data integrity at the
cost of the read performance.
For some use cases as
ping...
On 07/11/2014 05:59 PM, Gu Zheng wrote:
> Via implementing ACPI standard methods _EJ0 in ACPI table, after Guest OS
> remove
> one vCPU online, the fireware will store removed bitmap to QEMU, then QEMU
> could
> know to notify the assigned vCPU of exiting. meanwhile, intruduce the QOM
If a negative integer is used for the max_bytes parameter, QEMU currently
calls abort() and leaves behind a core dump. This patch adds a simple
error message to make the reason for the termination clearer.
Signed-off-by: John Snow
---
hw/virtio/virtio-rng.c | 6 +-
1 file changed, 5 insertio
On 14 July 2014 22:10, Alexander Graf wrote:
> On 07/14/2014 10:37 PM, Paolo Bonzini wrote:
>> But i2c is
>> simple enough, and there are so many devices with a 4-page datasheet,
>> that I think it would be acceptable. You could also write an i2c
>> passthrough chardev backend that connects to /d
Joakim Tjernlund/Transmode wrote on 2014/07/14 23:37:02:
> From: Joakim Tjernlund/Transmode
> To:
> Cc: Andreas Färber , Alexander Graf ,
qemu-devel@nongnu.org, Riku Voipio
> Date: 2014/07/14 23:37
> Subject: Re: [Qemu-devel] [PATCH v2] linux-user: make binfmt flag O
require P
>
> Joakim Tjer
Joakim Tjernlund/Transmode wrote on 2014/07/14 23:04:51:
> > Why do we need to modify argv[] here when we are building a
> > target_argv[] further down anyway?
> Because parse_opts() will not do it for me and I cannot figure out how
to modify
> parse_opts() whithout breaking it.
I took another l
On 07/14/2014 10:37 PM, Paolo Bonzini wrote:> The obvious thing to
consider is whether this could be used to
> circumvent the GPL.
>
> I think a generic memory-mapped I/O device interface is not a good idea
> in this respect, also because it's hard to get it right.
Okay, if this is a concern I wi
On 07/14/2014 10:41 AM, Bastian Koppelmann wrote:
> +target_ulong helper_shac(CPUTRICOREState *env, target_ulong r1,
> + target_ulong r2, target_ulong len)
> +{
> +target_ulong carry_out, msk, msk_start, msk_len, ret;
> +int32_t shift_count;
> +int const6;
> +
Andreas Färber wrote on 2014/07/14 22:14:25:
> Am 14.07.2014 20:52, schrieb Joakim Tjernlund:
> > Qemu can autodetect if it is started from Linux binfmt loader
>
> "QEMU"
>
> > when binfmt flag O is on.
> > Use that and require binfmt flag P as well which will enable QEMU
> > to pass in correct
On 14.07.14 19:24, Alexander Graf wrote:
On 14.07.14 15:30, Paolo Bonzini wrote:
Il 14/07/2014 15:13, Alexey Kardashevskiy ha scritto:
On 07/11/2014 01:03 AM, Alexey Kardashevskiy wrote:
This does small RMA allocation rework and enables huge pages.
Please comment, especially commit logs. Th
Previously, execute would be disabled for all pages with SMEP enabled,
regardless of what mode the access took place in.
Signed-off-by: Ricky Zhou
---
target-i386/helper.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/target-i386/helper.c b/target-i386/helper.c
index 11ca
Il 14/07/2014 20:09, Alexander Graf ha scritto:
So the protocol basically allows to forward read and write accesses on
IO memory to processes outside of Qemu.
Get and set transactions are triggered by Qemu on an IO memory read
operation or write operation respectively. The pipe communication blo
Il 14/07/2014 05:17, Alexey Kardashevskiy ha scritto:
> No, you should politely bother them again.
That does not seem helping though :-/
Sorry. :)
Well, patch 1 is the same as v6 and for the others Cornelia and Alex can
ack it. It looks good to me though.
Paolo
Am 14.07.2014 20:52, schrieb Joakim Tjernlund:
> Qemu can autodetect if it is started from Linux binfmt loader
"QEMU"
> when binfmt flag O is on.
> Use that and require binfmt flag P as well which will enable QEMU
> to pass in correct argv0 to the application.
>
> Signed-off-by: Joakim Tjernlund
Alexander Graf wrote on 2014/07/14 20:39:29:
>
> On 14.07.14 20:32, Joakim Tjernlund wrote:
> > Qemu can autodetect if it is started from Linux binfmt loader
> > when binfmt flag O is on.
> > Use that and require binfmt flag P as well which will enable QEMU
> > to pass in correct argv0 to the app
Qemu can autodetect if it is started from Linux binfmt loader
when binfmt flag O is on.
Use that and require binfmt flag P as well which will enable QEMU
to pass in correct argv0 to the application.
Signed-off-by: Joakim Tjernlund
---
linux-user/main.c | 13 -
scripts/qemu-
On 14.07.14 20:32, Joakim Tjernlund wrote:
Qemu can autodetect if it is started from Linux binfmt loader
when binfmt flag O is on.
Use that and require binfmt flag P as well which will enable QEMU
to pass in correct argv0 to the application.
Signed-off-by: Joakim Tjernlund
This is missing th
Qemu can autodetect if it is started from Linux binfmt loader
when binfmt flag O is on.
Use that and require binfmt flag P as well which will enable QEMU
to pass in correct argv0 to the application.
Signed-off-by: Joakim Tjernlund
---
linux-user/main.c | 13 -
1 file changed, 12 inse
On Mon, 14 Jul 2014 12:31:32 -0600
Eric Blake wrote:
> On 07/14/2014 12:12 PM, Luiz Capitulino wrote:
> Agree. Let's ditch nested structs and see whether there are any misuses
> of c_var() left.
> >>>
> >>> This is an honest question: do we really want to drop nested struct
> >>> supp
On 07/14/2014 12:12 PM, Luiz Capitulino wrote:
Agree. Let's ditch nested structs and see whether there are any misuses
of c_var() left.
>>>
>>> This is an honest question: do we really want to drop nested struct support,
>>> wasn't it added by the block layer or am I just confused?
>>
>>
i've followed the avices on Artyom Tarasenko's blog to install debian
wheezy sparc on qemu
but qemu won't boot the graphical installation
with -nographic the debian default installation seems to work
is this a known bug?
these are my installation steps
fresh ubuntu 14.04 x64 (3.13.0-30-generi
On Fri, 11 Jul 2014 15:22:24 -0600
Eric Blake wrote:
> On 07/11/2014 12:51 PM, Luiz Capitulino wrote:
>
> { 'type': 'VersionInfo',
> 'data': {'qemu': {'major': 'int', 'minor': 'int', 'micro': 'int'},
> + '__com.redhat.crap': {'major': 'int', 'minor': 'int',
> '
On 07/14/2014 01:46 PM, Paolo Bonzini wrote:
Il 13/07/2014 16:20, Alexander Graf ha scritto:
The
environment simulator is an external program which is connected to
several qemu instances via posix named pipes using a simple
communication protocol. Without pipe interaction the emulator can stil
On Fri, 11 Jul 2014 11:07:15 +0200
Markus Armbruster wrote:
> Cc'ing folks involved in the flawed commit.
>
> Liliang writes:
>
> > From: Li Liang
> >
> > This bug was introduced in the commit
> > 9005b2a7589540a3733b3abdcfbccfe7746cd1a1,
> > it will cause deadlock when create a vm with the
On 14.07.14 15:30, Paolo Bonzini wrote:
Il 14/07/2014 15:13, Alexey Kardashevskiy ha scritto:
On 07/11/2014 01:03 AM, Alexey Kardashevskiy wrote:
This does small RMA allocation rework and enables huge pages.
Please comment, especially commit logs. Thanks!
Changes:
v3:
* split to 2 patches, o
On 14.07.14 16:04, Mark Cave-Ayland wrote:
On 13/07/14 21:36, Alexander Graf wrote:
Mac OS X calibrates a number of frequencies on bootup based on reading
tb values on bootup and comparing them to via cuda timer values.
The only variable we can really steer well (thanks to KVM) is the cuda
fr
On 14.07.14 14:09, Gavin Shan wrote:
The permission of TCE entry should exclude physical base address.
Otherwise, unmapping TCE entry can be interpreted to mapping TCE
entry wrongly for VFIO devices.
Signed-off-by: Gavin Shan
Thanks, applied to ppc-next-2.1.
Alex
On 14.07.14 19:08, Joakim Tjernlund wrote:
Alexander Graf wrote on 2014/07/14 18:54:27:
0 is a valid fd :). And yes, this would work, but I don't see why we
should introduce the -binfmt-wrapper logic to upstream QEMU. It's never
been there. And the AT_EXECFD evaluation is a lot cleaner.
While
Alexander Graf wrote on 2014/07/14 18:54:27:
>
> 0 is a valid fd :). And yes, this would work, but I don't see why we
> should introduce the -binfmt-wrapper logic to upstream QEMU. It's never
> been there. And the AT_EXECFD evaluation is a lot cleaner.
>
> While we're at it - should we also pa
Alexander Graf wrote on 2014/07/14 18:54:27:
>
>
> On 14.07.14 18:51, Joakim Tjernlund wrote:
> > Alexander Graf wrote on 2014/07/14 18:34:34:
> >>
> >> On 14.07.14 18:32, Joakim Tjernlund wrote:
> >>> Alexander Graf wrote on 2014/07/14 18:00:35:
> >>> You think everyone feel OK with new defau
On 14.07.14 18:51, Joakim Tjernlund wrote:
Alexander Graf wrote on 2014/07/14 18:34:34:
On 14.07.14 18:32, Joakim Tjernlund wrote:
Alexander Graf wrote on 2014/07/14 18:00:35:
You think everyone feel OK with new defaults like OP ?
Yes.
hmm, with current qemu it works to boot a LXC with ju
Alexander Graf wrote on 2014/07/14 18:34:34:
>
>
> On 14.07.14 18:32, Joakim Tjernlund wrote:
> > Alexander Graf wrote on 2014/07/14 18:00:35:
> > You think everyone feel OK with new defaults like OP ?
> >> Yes.
> > hmm, with current qemu it works to boot a LXC with just O flag.
> > Why would w
Alexander Graf wrote on 2014/07/14 18:34:34:
>
>
> On 14.07.14 18:32, Joakim Tjernlund wrote:
> > Alexander Graf wrote on 2014/07/14 18:00:35:
> > You think everyone feel OK with new defaults like OP ?
> >> Yes.
> > hmm, with current qemu it works to boot a LXC with just O flag.
> > Why would w
Add instructions of SR opcode format.
Add micro-op generator functions for saturate.
Add helper return from exception (rfe).
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Change cdc_zero using clo32 instead of a loop.
- Change gen_saturate/_h using movecond instead of a branch.
-
Add basic softmmu support for TriCore
Signed-off-by: Bastian Koppelmann
---
target-tricore/helper.c| 54 +-
target-tricore/op_helper.c | 33 +++-
2 files changed, 85 insertions(+), 2 deletions(-)
diff --git a/target-tricore
Add instructions of SBR opcode format.
Add gen_loop micro-op generator function.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Change gen_loop() to subtract first and then compare to -1.
- Change gen_loop() using next_pc insted of insn_bytes.
- Change SBR_LOOP instructions to use
Add instructions of SB opcode format.
Add helper call/ret.
Add micro-op generator functions for branches.
Add makro to generate helper functions.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Fill in cdc_increment/cdc_decrement
- Replace save/restore_context with save/restore_context_
Hi,
my aim is to add Infineon's TriCore architecture to QEMU. This series of
patches adds the target stubs, a basic testboard and a softmmu for system mode
emulation. Furthermore it adds all the 16 bit long instructions of the
architecture grouped by opcode format.
After this series of patches
Add instructions of SSR opcode format.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Remove AND in ST_B and ST_H instructions.
- Load/Store instructions now use new TCGMemOp.
- Move SSR instructions to one decode function.
target-tricore/translate.c | 50
Add instructions of SRR opcode format.
Add helper for add/sub_ssov.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Replace gen_ssov with helper for add_ssov and sub_ssov.
- Move SRR instructions to one decode function.
target-tricore/helper.h| 2 +
target-tricore/op_helper.c |
Add instructions of SLR, SSRO and SRO opcode format.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Add one decode function for all SLR instructions.
- Add one decode function for all SRO instructions.
- Remove duplicate SSRO instructions, which were removed in patch v1 15/15.
Add instructions of SSRS and SLRO opcode format.
Add micro-op generator functions for offset loads.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Replace OP_MEM_INDIRECT with gen_offset_ld/st functions using TCGMemOp.
- Change load/store instructions to use TCGMemOp.
target-tricore/
Add instructions of SBC and SBRN opcode format.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Change compare to 0 at instructions JZ_T and JNZ_T.
- Group SBC instructions to one case.
- Group SBRN instructions to one case.
target-tricore/translate.c | 35
Add basic board to allow systemmode emulation
Signed-off-by: Bastian Koppelmann
---
hw/tricore/Makefile.objs | 1 +
hw/tricore/tricore_testboard.c | 130 +
include/hw/tricore/tricore.h | 54 +
3 files changed, 185 insertions(+)
Add tcg and cpu model initialization.
Add gen_intermediate_code function.
Activate target in configure and add softmmu config.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Add next_pc to DisasContext and change pc calculation.
- Remove insn_bytes.
configure
Add TriCore target stubs, and QOM cpu.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Move activation of target patch1->patch4.
- Remove host related in configure.
- Remove host related code in user-exec.
- Remove active_tc struct.
- Change define GPR first, then CSFR.
Add instructions of SC opcode format.
Add helper for begin interrupt service routine.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- Add save_context_lower. (see patch v2 10/15)
- Remove printfs in helper_bisr.
- Add one decode function for all SC instructions.
target-tricore/hel
Add instructions of SRC opcode format.
Add helper for sh arithmetic carry.
Add micro-op generator functions for conditional add/sub and shi.
Signed-off-by: Bastian Koppelmann
---
v1 -> v2:
- helper_shac uses sextract32 for the constant and add len parameter.
- Replace else case with signe
Hello engineers,
could you please help me locating the place in qemu (qemu-kvm) source
where the memory for virtual machine is requested from operating
system [1].
Thank you in advance.
[1] http://www.linux-kvm.org/page/Memory
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov /
On 14.07.14 18:32, Joakim Tjernlund wrote:
Alexander Graf wrote on 2014/07/14 18:00:35:
You think everyone feel OK with new defaults like OP ?
Yes.
hmm, with current qemu it works to boot a LXC with just O flag.
Why would we then want to complicate things by adding OP which
then requires some
Signed-off-by: Leon Alrae
---
target-mips/translate_init.c | 11 +--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/target-mips/translate_init.c b/target-mips/translate_init.c
index bcfc46a..0b70d05 100644
--- a/target-mips/translate_init.c
+++ b/target-mips/translate_i
Alexander Graf wrote on 2014/07/14 18:00:35:
>
>
> On 14.07.14 17:59, Joakim Tjernlund wrote:
> > Alexander Graf wrote on 2014/07/14 17:46:18:
> >>
> >> On 14.07.14 17:38, Joakim Tjernlund wrote:
> >>> Alexander Graf wrote on 2014/07/14 17:21:33:
> >>>
> From: Alexander Graf
> To: J
Signed-off-by: Leon Alrae
---
target-mips/cpu.h |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/target-mips/cpu.h b/target-mips/cpu.h
index a35ab9d..b981ec7 100644
--- a/target-mips/cpu.h
+++ b/target-mips/cpu.h
@@ -789,7 +789,8 @@ static inline void compute_hflags(CPU
Release 6 limits the number of cases where software can cause UNDEFINED or
UNPREDICTABLE behaviour. In this case, when accessing reserved / unimplemented
CP0 register, writes are ignored and reads return 0.
In pre-R6 the behaviour is not specified, but generating RI exception is not
what the real
When conditional compact branch is encountered decode one more instruction in
current translation block - that will be forbidden slot. Instruction in
forbidden slot will be executed only if conditional compact branch is not taken.
Any control transfer instruction (CTI) which are branches, jumps, E
SDBBP instruction Reserved Instruction control. The purpose of this field is
to restrict availability of SDBBP to kernel mode operation.
If the bit is set then SDBBP instruction can only be executed in kernel mode.
User execution of SDBBP will cause a Reserved Instruction exception.
Signed-off-by
In Release 6 not all the values are allowed to be written to a register.
If the value is not valid or unsupported then it should stay unchanged.
For pre-R6 the existing behaviour has been changed only for CP0_Index register
as the current implementation does not seem to be correct - it looks like
This patchset provides the following set of features:
- forbidden slot
- Config5.SBRI bit
- reserved fields and reserved registers (ignore write, read 0)
- updated MIPS64R6-generic CPU
It also includes modification of the behaviour when accessing unimplemented
CP0 register - the Reserved Instructi
Peter Maydell wrote on 2014/07/14 18:00:38:
>
> On 14 July 2014 16:59, Joakim Tjernlund
wrote:
> > scripts/qemu-binfmt-conf.sh does not use any flag currently, I don't
think
> > that works either with current linux-user and choot/lxc
>
> That script is pretty awful and no sane distro is going
Hi,
> > For anything using kernel 3.14+ IMO the answer to pretty much *any* gfx
> > issue is "use stdvga instead of cirrus". 3.14 got a kms driver for the
> > qemu stdvga (bochsdrm), so the modesetting driver and all the modern
> > stuff such as root-less X server works with the stdvga too. An
On 14 July 2014 16:59, Joakim Tjernlund wrote:
> scripts/qemu-binfmt-conf.sh does not use any flag currently, I don't think
> that works either with current linux-user and choot/lxc
That script is pretty awful and no sane distro is going to use
it anyhow...
-- PMM
On 14.07.14 17:59, Joakim Tjernlund wrote:
Alexander Graf wrote on 2014/07/14 17:46:18:
On 14.07.14 17:38, Joakim Tjernlund wrote:
Alexander Graf wrote on 2014/07/14 17:21:33:
From: Alexander Graf
To: Joakim Tjernlund ,
Cc: qemu-devel@nongnu.org
Date: 2014/07/14 17:21
Subject: Re: [PATCH
Alexander Graf wrote on 2014/07/14 17:46:18:
>
>
> On 14.07.14 17:38, Joakim Tjernlund wrote:
> > Alexander Graf wrote on 2014/07/14 17:21:33:
> >
> >> From: Alexander Graf
> >> To: Joakim Tjernlund ,
> >> Cc: qemu-devel@nongnu.org
> >> Date: 2014/07/14 17:21
> >> Subject: Re: [PATCH] linux-us
On 14/07/14 15:35, Peter Maydell wrote:
> On 14 July 2014 14:33, James Hogan wrote:
>> On 10/07/14 13:17, Peter Maydell wrote:
>>> More generally, there doesn't really seem to be provision in the
>>> KVM KVM_EXIT_MMIO API for returning "this access failed".
>>> I guess in theory userspace could do
From: Fam Zheng
In the case that the lun number is taken by another scsi device, don't
release the existing device siliently, but report an error to user.
Signed-off-by: Fam Zheng
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-bus.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
qemu_chr_be_generic_open cannot be called with the write lock taken,
because it calls client code that may call qemu_chr_fe_write. This
actually happens for the monitor:
0x727dbf79 in __GI_raise (sig=sig@entry=6)
0x727df388 in __GI_abort ()
0x555ef489 in error_
Otherwise, hot-unplug of pci-serial-2x trips the assertion
in memory_region_destroy:
(qemu) device_del gg
(qemu) qemu-system-x86_64: /work/armbru/tmp/qemu/memory.c:1021:
memory_region_destroy: Assertion `((&mr->subregions)->tqh_first == ((void
*)0))' failed.
Aborted (core dumped)
Re
From: Kirill Batuzov
Whenever serial_xmit fails to transmit a byte it adds a watch that would
call it again when the "line" becomes ready. This results in a retry
chain:
serial_xmit -> add_watch -> serial_xmit
Each chain is able to transmit one character, and for every character
passed to seria
Right now starting a machine with virtio-scsi and a <= 2.0 machine type
fails with:
qemu-system-x86_64: -device virtio-scsi-pci: Property .any_layout not found
This is because the any_layout bit was actually never set after
virtio-scsi was changed to support arbitrary layout for virtio buffer
The following changes since commit ab6d3749c4915cd5692633e321f7745dce06fe77:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20140711-1' into
staging (2014-07-11 17:50:38 +0100)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
for you
Il 14/07/2014 17:38, Andreas Färber ha scritto:
The libqos implementation of io_read{b,w,l} and io_write{b,w,l} hooks
was relying on qtest_mem{read,write}() respectively. With d81d410 (usb:
improve ehci/uhci test) this resulted in assertion failures on ppc hosts:
ERROR:tests/usb-hcd-ehci-test.c
On 14.07.14 17:38, Joakim Tjernlund wrote:
Alexander Graf wrote on 2014/07/14 17:21:33:
From: Alexander Graf
To: Joakim Tjernlund ,
Cc: qemu-devel@nongnu.org
Date: 2014/07/14 17:21
Subject: Re: [PATCH] linux-user: Add binfmt wrapper
On 14.07.14 16:38, Joakim Tjernlund wrote:
The popular b
Alexander Graf wrote on 2014/07/14 17:21:33:
> From: Alexander Graf
> To: Joakim Tjernlund ,
> Cc: qemu-devel@nongnu.org
> Date: 2014/07/14 17:21
> Subject: Re: [PATCH] linux-user: Add binfmt wrapper
>
>
> On 14.07.14 16:38, Joakim Tjernlund wrote:
> > The popular binfmt-wrapper patch adds an
The libqos implementation of io_read{b,w,l} and io_write{b,w,l} hooks
was relying on qtest_mem{read,write}() respectively. With d81d410 (usb:
improve ehci/uhci test) this resulted in assertion failures on ppc hosts:
ERROR:tests/usb-hcd-ehci-test.c:78:ehci_port_test: assertion failed: ((value &
m
On Mon, 2014-07-14 at 22:09 +1000, Gavin Shan wrote:
> The permission of TCE entry should exclude physical base address.
> Otherwise, unmapping TCE entry can be interpreted to mapping TCE
> entry wrongly for VFIO devices.
>
> Signed-off-by: Gavin Shan
> ---
> hw/misc/vfio.c | 2 +-
> hw/pp
Peter Crosthwaite writes:
> On Thu, Jun 26, 2014 at 5:32 PM, Markus Armbruster wrote:
>> Paolo Bonzini writes:
>>
>>> Otherwise, hot-unplug of pci-serial-2x trips the assertion
>>> in memory_region_destroy:
>>>
>>> (qemu) device_del gg
>>> (qemu) qemu-system-x86_64: /work/armbru/tmp/qem
Am 14.07.2014 15:12, schrieb Alexey Kardashevskiy:
> On 07/14/2014 06:14 PM, Paolo Bonzini wrote:
>> Il 13/07/2014 16:41, Alexey Kardashevskiy ha scritto:
>>> Current object_child_foreach() uses QTAILQ_FOREACH() to walk
>>> through children and that makes children removal from the callback
>>> impo
On 14.07.14 16:38, Joakim Tjernlund wrote:
The popular binfmt-wrapper patch adds an additional
executable which mangle argv suitable for binfmt flag P.
In a chroot you need the both (statically linked) qemu-$arch
and qemu-$arch-binfmt-wrapper. This is sub optimal and a
better approach is to reco
On 14 July 2014 15:35, Dmitry Poletaev wrote:
> I executed test-i386 from tests folder from QEMU rep and according to the
> result, instructions fistl and fistpll returns maximum positive result
> (0x7fff...), if a FPU register stores a positive infinity, and minimum
> negative result (0x80...)
On 14 July 2014 12:42, Kevin Wolf wrote:
> v2:
> - Fixed assertion failure on 32 bit hosts triggered by qtests
> (32 bit truncation of image file size in patch "block: Make qiov
> match the request size until EOF")
>
>
> The following changes since commit 675879f6f3c9463e103735a4e41e9deb0bee9b
The popular binfmt-wrapper patch adds an additional
executable which mangle argv suitable for binfmt flag P.
In a chroot you need the both (statically linked) qemu-$arch
and qemu-$arch-binfmt-wrapper. This is sub optimal and a
better approach is to recognize the -binfmt-wrapper extension
within lin
On 14 July 2014 14:33, James Hogan wrote:
> On 10/07/14 13:17, Peter Maydell wrote:
>> More generally, there doesn't really seem to be provision in the
>> KVM KVM_EXIT_MMIO API for returning "this access failed".
>> I guess in theory userspace could do all the "figure out how
>> to adjust CPU stat
I executed test-i386 from tests folder from QEMU rep and according to the
result, instructions fistl and fistpll returns maximum positive result
(0x7fff...), if a FPU register stores a positive infinity, and minimum negative
result (0x80...), if a negative infinity stores in a register. Real pro
On Tue, Jul 15, 2014 at 12:20 AM, Paolo Bonzini wrote:
> Il 14/07/2014 14:36, Peter Crosthwaite ha scritto:
>
>> On Thu, Jun 26, 2014 at 5:32 PM, Markus Armbruster
>> wrote:
>>>
>>> Paolo Bonzini writes:
>>>
Otherwise, hot-unplug of pci-serial-2x trips the assertion
in memory_region_de
Il 14/07/2014 14:36, Peter Crosthwaite ha scritto:
On Thu, Jun 26, 2014 at 5:32 PM, Markus Armbruster wrote:
Paolo Bonzini writes:
Otherwise, hot-unplug of pci-serial-2x trips the assertion
in memory_region_destroy:
(qemu) device_del gg
(qemu) qemu-system-x86_64: /work/armbru/tmp/qe
On 14/07/14 15:00, Alexander Graf wrote:
On 14.07.14 15:58, Mark Cave-Ayland wrote:
On 13/07/14 17:17, Alexander Graf wrote:
While trying to get Mac OS X booting with our -M mac99 emulation I
stumbled
over a few issues that prevented it from doing so.
With these patches applied I still can't
On 13/07/14 21:36, Alexander Graf wrote:
Mac OS X calibrates a number of frequencies on bootup based on reading
tb values on bootup and comparing them to via cuda timer values.
The only variable we can really steer well (thanks to KVM) is the cuda
frequency. So let's use that one to fake Mac OS
On 14.07.14 15:58, Mark Cave-Ayland wrote:
On 13/07/14 17:17, Alexander Graf wrote:
While trying to get Mac OS X booting with our -M mac99 emulation I
stumbled
over a few issues that prevented it from doing so.
With these patches applied I still can't properly boot Mac OS X with
-M mac99,
b
On 13/07/14 17:17, Alexander Graf wrote:
While trying to get Mac OS X booting with our -M mac99 emulation I stumbled
over a few issues that prevented it from doing so.
With these patches applied I still can't properly boot Mac OS X with -M mac99,
but I get a lot further than before. The biggest
1 - 100 of 189 matches
Mail list logo
