Hello everyone,
I'm a newcomer in QEMU and my goal would be to port an existing system
simulator using another emulator to QEMU.
Some work has already been done, and Sparc has been the main target so
far because of its simplicity (and because we have a very good support
for Sparc with the othe
> > Running barebox on qemu-system-mips* with '-d unimp' overloads
> > stderr by very very many mips_cpu_handle_mmu_fault() messages:
> >
> > mips_cpu_handle_mmu_fault address=b80003fd ret 0 physical
> > 180003fd
> > prot 3
> > mips_cpu_handle_mmu_fault address=a0800884 ret 0 physic
On 11/05/2014 06:35 PM, Alex Williamson wrote:
> Hi Eric,
>
> On Fri, 2014-10-31 at 14:05 +, Eric Auger wrote:
>> Introduce the VFIODevice struct that is going to be shared by
>> VFIOPCIDevice and VFIOPlatformDevice.
>>
>> Additional fields will be added there later on for review
>> convenienc
On 11/05/2014 11:23 PM, Alexander Graf wrote:
>
>
> On 05.11.14 13:31, Eric Auger wrote:
>> On 11/05/2014 11:59 AM, Alexander Graf wrote:
>>>
>>>
>>> On 31.10.14 15:05, Eric Auger wrote:
vfio-calxeda-xgmac now can be instantiated using the -device option.
The node creation function gene
Gerd Hoffmann writes:
> On Mi, 2014-11-05 at 00:49 +0800, Amos Kong wrote:
>> qemu_input_find_handler() prefers a handler associated with con.
>> But if none exists, it takes any. This patch added a parameter
>> to strictly check console, in case we want to input event to
>> special console.
>>
> -Original Message-
> From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> Sent: Monday, November 03, 2014 7:54 PM
> To: Xu, Quan
> Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org;
> stefano.stabell...@eu.citrix.com
> Subject: Re: [PATCH 2/4] Qemu-Xen-vTPM: Register Xe
On Thu, Nov 06, 2014 at 10:38:34AM +0900, SeokYeon Hwang wrote:
> Please review this patch.
>
> Thanks.
Thanks for the patch!
Sorry, this patch missed the devel freeze.
Please resubmit after 2.2 is out.
> > -Original Message-
> > From: SeokYeon Hwang [mailto:syeon.hw...@samsung.com]
> >
SeokYeon Hwang writes:
>> -Original Message-
>> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
>> Bonzini
>> Sent: Wednesday, November 05, 2014 11:55 PM
>> To: Michael S. Tsirkin
>> Cc: Markus Armbruster; SeokYeon Hwang; qemu-devel@nongnu.org
>> Subject: Re: [Qemu
On Thu, Nov 06, 2014 at 11:26:01AM +0900, SeokYeon Hwang wrote:
>
>
> > -Original Message-
> > From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> > Bonzini
> > Sent: Wednesday, November 05, 2014 11:55 PM
> > To: Michael S. Tsirkin
> > Cc: Markus Armbruster; SeokYeon
On Wed, Nov 05, 2014 at 03:35:09PM -0500, Paul Moore wrote:
> On Wednesday, November 05, 2014 08:08:06 PM Peter Maydell wrote:
> > On 5 November 2014 19:46, Paul Moore wrote:
> > > On Wednesday, November 05, 2014 05:08:20 PM Peter Maydell wrote:
> > >> On 5 November 2014 16:47, Eduardo Otubo wrote
On 2014-10-28 at 11:12, Max Reitz wrote:
The block layer read and write functions do not like requests which are
bigger than INT_MAX bytes. Since the VDI bmap is read and written in a
single operation, its size is therefore limited accordingly. This
reduces the maximum VDI image size supported by
On 2014/11/6 9:59, Shannon Zhao wrote:
>
>
> On 2014/11/5 16:43, Eric Auger wrote:
>> On 10/27/2014 12:23 PM, Li Liu wrote:
>>>
>>>
>>> On 2014/10/27 17:37, Peter Maydell wrote:
On 25 October 2014 09:24, john.liuli wrote:
> To get the interrupt reason to support such VIRTIO_NET_F_STAT
SeokYeon Hwang writes:
>> -Original Message-
>> From: SeokYeon Hwang [mailto:syeon.hw...@samsung.com]
>> Sent: Wednesday, November 05, 2014 10:13 PM
>> To: 'Paolo Bonzini'; 'Max Reitz'; 'qemu-devel@nongnu.org'
>> Cc: 'arm...@redhat.com'; 'paolo.bonz...@gmail.com'
>> Subject: RE: [PATCH] e
On Thu, Nov 06, 2014 at 10:20:32AM +0100, Markus Armbruster wrote:
> SeokYeon Hwang writes:
>
> >> -Original Message-
> >> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> >> Bonzini
> >> Sent: Wednesday, November 05, 2014 11:55 PM
> >> To: Michael S. Tsirkin
> >>
On Tue, Nov 04, 2014 at 05:35:12PM +0800, Shannon Zhao wrote:
> As the current virtio-mmio only support single irq,
> so some advanced features such as vhost-net with irqfd
> are not supported. And the net performance is not
> the best without vhost-net and irqfd supporting.
>
> This patch support
> -Original Message-
> From: Markus Armbruster [mailto:arm...@redhat.com]
> Sent: Thursday, November 06, 2014 6:21 PM
> To: SeokYeon Hwang
> Cc: 'Paolo Bonzini'; 'Michael S. Tsirkin'; qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] [PATCH] pci: fixed mismatch of error-handling
> between p
> -Original Message-
> From: Michael S. Tsirkin [mailto:m...@redhat.com]
> Sent: Thursday, November 06, 2014 6:17 PM
> To: SeokYeon Hwang
> Cc: qemu-devel@nongnu.org; aneesh.ku...@linux.vnet.ibm.com;
> pbonz...@redhat.com; Peter Maydell
> Subject: Re: [PATCH] 9pfs: changed to use event_noti
On 2014/11/6 17:34, Michael S. Tsirkin wrote:
> On Tue, Nov 04, 2014 at 05:35:12PM +0800, Shannon Zhao wrote:
>> As the current virtio-mmio only support single irq,
>> so some advanced features such as vhost-net with irqfd
>> are not supported. And the net performance is not
>> the best without vho
On Wednesday 05 November 2014 09:16 PM, Tom Musta wrote:
> On 11/5/2014 2:32 AM, Alexander Graf wrote:
>>
>>
>> On 05.11.14 08:13, Aravinda Prasad wrote:
>>> This patch adds FWNMI support in qemu for powerKVM
>>> guests by handling the ibm,nmi-register rtas call.
>>> Whenever OS issues ibm,nmi-re
> Am 06.11.2014 um 09:11 schrieb Antony Pavlov :
>
>
>>> Running barebox on qemu-system-mips* with '-d unimp' overloads
>>> stderr by very very many mips_cpu_handle_mmu_fault() messages:
>>>
>>> mips_cpu_handle_mmu_fault address=b80003fd ret 0 physical 180003fd
>>> prot 3
>>> mips_
On Wed, Nov 5, 2014 at 1:26 PM, Claudio Fontana
wrote:
> On 11.07.2014 09:21, Alvise Rigo wrote:
>> Keeping advantage of the finalize_dt QEMUMachine function, the mach-virt
>> machine now completes the device tree creation after that all the
>> generic devices have been instantiated. This allows t
> Am 06.11.2014 um 11:00 schrieb Aravinda Prasad :
>
>
>
>> On Wednesday 05 November 2014 09:16 PM, Tom Musta wrote:
>>> On 11/5/2014 2:32 AM, Alexander Graf wrote:
>>>
>>>
On 05.11.14 08:13, Aravinda Prasad wrote:
This patch adds FWNMI support in qemu for powerKVM
guests by
New R6 COP1 conditional branches currently don't have delay slot. Fixing this
by setting MIPS_HFLAG_BDS32 flag which is required for branches having 4-byte
delay slot.
Signed-off-by: Leon Alrae
---
target-mips/translate.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/target-mips/translate.
On Thursday 06 November 2014 03:59 PM, Alexander Graf wrote:
>
>
>
>> Am 06.11.2014 um 11:00 schrieb Aravinda Prasad :
>>
>>
>>
[...]
>>>
>>> And, perhaps this was discussed in an earlier patch, but couldn't you just
>>> do:
>>>
>>>li 3,KVMPPC_H_REPORT_MC_ERR
>>>
>>> here and avoid the
On 06/11/2014 10:29, Leon Alrae wrote:
New R6 COP1 conditional branches currently don't have delay slot. Fixing this
by setting MIPS_HFLAG_BDS32 flag which is required for branches having 4-byte
delay slot.
Signed-off-by: Leon Alrae
---
target-mips/translate.c | 1 +
1 file changed, 1 insert
On Thu, Nov 06, 2014 at 05:54:54PM +0800, Shannon Zhao wrote:
> On 2014/11/6 17:34, Michael S. Tsirkin wrote:
> > On Tue, Nov 04, 2014 at 05:35:12PM +0800, Shannon Zhao wrote:
> >> As the current virtio-mmio only support single irq,
> >> so some advanced features such as vhost-net with irqfd
> >> a
This feature can help to reduce the data transferred about 60%, and the
migration time can also be reduced about 70%.
Summary of changed from v1->v2
-Changed the decompression thread limit from 64 to 255
-Fixed some spelling mistake
-Added test result to the document
-Fixe
Give some details about the multiple compression threads and how
to use it in live migration.
Signed-off-by: Li Liang
---
docs/multiple-compression-threads.txt | 128 ++
1 file changed, 128 insertions(+)
create mode 100644 docs/multiple-compression-threads.txt
d
Instead of sending the guest memory directly, this solution compress
the ram page before sending, after receiving, the data will be
decompressed.
This feature can help to reduce the data transferred about
60%, this is very useful when the network bandwidth is limited,
and the migration time can als
Users of virtio-serial may want to know when a port becomes writable. A
port can stop accepting writes if the guest port is open but not being
read from. In this case, data gets queued up in the virtqueue, and
after the vq is full, writes to the port do not succeed.
When the guest reads off a vq
The following changes since commit 6e76d125f244e10676b917208f2a074729820246:
Update version for v2.2.0-rc0 release (2014-11-05 15:21:04 +)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/qemu/amit/virtio-serial.git
tags/vser-2.2.0-queue
for you to fetch change
From: Marc-André Lureau
It seems "name" is not mandatory, and the following command line (based
on one generated by current libvirt) will crash qemu at start:
qemu-system-x86_64 \
-device virtio-serial-pci \
-device virtserialport,name=foo \
-device virtconsole
Program received sign
On 11/06/2014 12:08 PM, Li Liang wrote:
> Give some details about the multiple compression threads and how
> to use it in live migration.
>
> Signed-off-by: Li Liang
> ---
> docs/multiple-compression-threads.txt | 128
> ++
> 1 file changed, 128 insertions(+)
>
On 05/11/2014 17:43, Richard Henderson wrote:
On 10/29/2014 02:41 AM, Yongbok Kim wrote:
+void helper_msa_shf_df(CPUMIPSState *env, uint32_t df, uint32_t wd,
+ uint32_t ws, uint32_t imm)
+{
+wr_t *pwd = &(env->active_fpu.fpr[wd].wr);
+wr_t *pws = &(env->active_fpu.f
Max Reitz writes:
> On 2014-11-04 at 19:45, Markus Armbruster wrote:
>> I'll try to explain all solutions fairly. Isn't easy when you're as
>> biased towards one of them as I am. Please bear with me.
>>
>>
>> = The trust boundary between image contents and meta-data =
>>
>> A disk image consist
On 06.11.14 09:57, Eric Auger wrote:
> On 11/05/2014 11:23 PM, Alexander Graf wrote:
>>
>>
>> On 05.11.14 13:31, Eric Auger wrote:
>>> On 11/05/2014 11:59 AM, Alexander Graf wrote:
On 31.10.14 15:05, Eric Auger wrote:
> vfio-calxeda-xgmac now can be instantiated using the -devi
Eric Blake writes:
> On 11/05/2014 09:38 AM, Max Reitz wrote:
>
>>> Note that specifying just the top image's format is not enough, you also
>>> have to specify any backing images' formats. QCOW2 can optionally store
>>> the backing image format in the image. The other COW formats can't.
>>
>>
On 5 November 2014 09:58, Claudio Fontana wrote:
> Please correct me if I am wrong, my understanding at the moment is that
> for X86 there is an ACPI implementation in hw/acpi, with the table generation
> happening in hw/i386/acpi-build.c .
> Couldn't there be some unification where part of the in
On 6 November 2014 11:20, Amit Shah wrote:
> The following changes since commit 6e76d125f244e10676b917208f2a074729820246:
>
> Update version for v2.2.0-rc0 release (2014-11-05 15:21:04 +)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/virt/qemu/amit/virtio-ser
Unfortunately, old guest OSes do not align partitions to page size by
default. This is true for Windows 2003 and Windows XP.
"Padding" is a value which should be added to guest LBA to obtain
sector number inside the image. This results in a shifted images.
0123offset inside image (in 51
Signed-off-by: Denis V. Lunev
Acked-by: Roman Kagan
Reviewed-by: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
tests/qemu-iotests/076| 6 ++
tests/qemu-iotests/076.out| 4
tests/qemu-iotests/sample_images/para
Typically Parallels disk bundle consists of several images which are
glued by XML disk descriptor. Also XML hides inside several important
parameters which are not available in the image header.
This patch allows to specify this XML file as a filename for an image
to open. It is allowed only to op
Signed-off-by: Denis V. Lunev
Acked-by: Roman Kagan
Reviewed-by: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
block/parallels.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/block/parallels.c b/block/parallels.c
index b27d1ea..7622f64 100644
--- a/block/parallels.
Eric Blake writes:
> On 11/04/2014 07:45 PM, Markus Armbruster wrote:
>> I'll try to explain all solutions fairly. Isn't easy when you're as
>> biased towards one of them as I am. Please bear with me.
>>
>
> Thanks for this write-up. I'll probably reply again, but for now I'm
> focusing on ju
This dependency is required for adequate Parallels images support.
Typically the disk consists of several images which are glued by
XML disk descriptor. Also XML hides inside several important parameters
which are not available in the image header.
The patch also adds clause to checkpatch.pl to un
suggested by Jeff Cody
Signed-off-by: Denis V. Lunev
CC: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
tests/qemu-iotests/076 | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tests/qemu-iotests/076 b/tests/qemu-iotests/076
index ed2be35..0139976 100755
--- a/t
On 2014-11-06 at 13:26, Markus Armbruster wrote:
Max Reitz writes:
On 2014-11-04 at 19:45, Markus Armbruster wrote:
I'll try to explain all solutions fairly. Isn't easy when you're as
biased towards one of them as I am. Please bear with me.
= The trust boundary between image contents and
The patchset implements additional compatibility bits for Parallels
format:
- initial support of parsing of Parallels DiskDeskriptor.xml
Typically Parallels disk bundle consists of several images which are
glued by XML disk descriptor. Also XML hides inside several important
parameters which
Unfortunately, old guest OSes do not align partitions to page size by
default. This is true for Windows 2003 and Windows XP.
For the time being Parallels was created an optimization for such OSes
in its desktop product. Desktop users are not qualified enough to create
properly aligned installation
On Thu, 6 Nov 2014 12:44:04 +
Peter Maydell wrote:
> On 5 November 2014 09:58, Claudio Fontana wrote:
> > Please correct me if I am wrong, my understanding at the moment is that
> > for X86 there is an ACPI implementation in hw/acpi, with the table
> > generation
> > happening in hw/i386/ac
On 11/06/2014 12:08 PM, Li Liang wrote:
> Instead of sending the guest memory directly, this solution compress
> the ram page before sending, after receiving, the data will be
> decompressed.
> This feature can help to reduce the data transferred about
> 60%, this is very useful when the network ba
On 11/06/2014 01:43 PM, Markus Armbruster wrote:
>> Actually, qed requires the backing format to be recorded (it is
>> non-optional) and is therefore immune to probing problems of backing
>> files. That's one thing it got right.
>
> If I read the code correctly:
>
> QED has a feature bit QED_F_
Am 06.11.2014 um 13:26 hat Markus Armbruster geschrieben:
> >> * Reuse the image *without* specifying the raw format. QEMU guesses the
> >>format based on untrusted image contents. Now QEMU guesses a format
> >>chosen by the guest, with meta-data chosen by the guest. By
> >>controlli
"Dr. David Alan Gilbert" writes:
> * Markus Armbruster (arm...@redhat.com) wrote:
>> I'll try to explain all solutions fairly. Isn't easy when you're as
>> biased towards one of them as I am. Please bear with me.
>>
>>
>> = The trust boundary between image contents and meta-data =
>>
>> A di
On Tue, Oct 28, 2014 at 11:12:32AM +0100, Max Reitz wrote:
> The block layer read and write functions do not like requests which are
> bigger than INT_MAX bytes. Since the VDI bmap is read and written in a
> single operation, its size is therefore limited accordingly. This
> reduces the maximum VDI
* Li Liang (liang.z...@intel.com) wrote:
> Give some details about the multiple compression threads and how
> to use it in live migration.
>
> Signed-off-by: Li Liang
> ---
> docs/multiple-compression-threads.txt | 128
> ++
> 1 file changed, 128 insertions(+)
>
On 06.11.2014 14:06, Stefan Hajnoczi wrote:
On Tue, Oct 28, 2014 at 11:12:32AM +0100, Max Reitz wrote:
The block layer read and write functions do not like requests which are
bigger than INT_MAX bytes. Since the VDI bmap is read and written in a
single operation, its size is therefore limited ac
On Thu, Nov 06, 2014 at 06:53:03AM +, Hanjun Guo wrote:
> On 2014-10-31 2:02, Mark Rutland wrote:
> > On Thu, Oct 30, 2014 at 05:52:44PM +, Peter Maydell wrote:
> >> On 30 October 2014 17:43, Alexander Spyridakis
> >> wrote:
> >>> Currently, the virt machine model generates Device Tree inf
On 6 November 2014 14:44, Peter Maydell wrote:
>
>
> > We need ACPI guest support in QEMU for AArch64 over here, with all features
> > (including the ability to run ACPI code and add specific tables), for
> > ACPI-based guests.
>
> The plan for providing ACPI to guests is that we run a UEFI BIOS
>
On Thursday 06 November 2014 13:30:01 Mark Rutland wrote:
>
> There is no way of doing this with DT. There has been work into DT
> fragments/overlays where portions can be added to the tree dynamically,
> but that's controlled by the OS rather than the hypervisor, and there's
> no standard for com
On 11/06/2014 02:24 PM, Dr. David Alan Gilbert wrote:
> * Li Liang (liang.z...@intel.com) wrote:
>> Give some details about the multiple compression threads and how
>> to use it in live migration.
>>
>> Signed-off-by: Li Liang
>> ---
>> +TODO
>> +
>> +Some faster compression/decompression met
On 6 November 2014 13:33, Alexander Spyridakis
wrote:
> The rational in the proposed approach is meant for cases where the
> user does not want to rely on external firmware layers. While UEFI
> could do what you are describing, the point is to avoid this not so
> trivial overhead in the booting pr
Kevin Wolf writes:
> Am 04.11.2014 um 19:45 hat Markus Armbruster geschrieben:
>> I'll try to explain all solutions fairly. Isn't easy when you're as
>> biased towards one of them as I am. Please bear with me.
>>
>>
>> = The trust boundary between image contents and meta-data =
>>
>> A disk
On 11/06/2014 02:57 PM, Markus Armbruster wrote:
>> Yes, you can override the backing file driver (backing.driver=raw should
>> do the trick). Not really user-friendly, especially with long backing
>> file chains, but it happens to be there.
>>
>> And of course, libvirt should be using it for non-
Fix build failure that would be caused by missing pc_dimm_count()
that was introduced in dropped
[03/11] pc: check if KVM has enough memory slots for DIMM devices
Signed-off-by: Igor Mammedov
---
hw/i386/pc.c | 12
1 file changed, 12 insertions(+)
diff --git a/hw/i386/pc.c b/hw/i
Now qemu only supports vhd type VHD_FIXED and VHD_DYNAMIC, so qemu
can't read snapshot volume of vhd, and can't support other storage
features of vhd file.
This patch add read parent information in function "vpc_open", read
bitmap in "vpc_read", and change bitmap in "vpc_write".
Signed-off-by: Xi
On 2014-10-31 2:02, Mark Rutland wrote:
> On Thu, Oct 30, 2014 at 05:52:44PM +, Peter Maydell wrote:
>> On 30 October 2014 17:43, Alexander Spyridakis
>> wrote:
>>> Currently, the virt machine model generates Device Tree information
>>> dynamically based on the existing devices in the system.
On Thu, Nov 06, 2014 at 02:57:07PM +0100, Markus Armbruster wrote:
> Kevin Wolf writes:
>
> > Am 04.11.2014 um 19:45 hat Markus Armbruster geschrieben:
[...]
> >> I proposed something less radical, namely to keep guessing the image
> >> format, but base the guess on trusted meta-data only: file
Now qemu only supports vhd type VHD_FIXED and VHD_DYNAMIC, so qemu
can't read snapshot volume of vhd, and can't support other storage
features of vhd file.
This patch add read parent information in function "vpc_open", read
bitmap in "vpc_read", and change bitmap in "vpc_write".
Signed-off-by: Xi
Right now seccomp is breaking the compilation of Qemu on armv7l due
to libsecomp current lack of support for this arch. This problem is
already fixed on libseccomp upstream but no release date for that is
scheduled to far. This patch disables support for seccomp on armv7l
temporarily until libsecco
I spent some time with Andrei Ostanin's "Playing with Mac OS X on KVM"
(http://blog.ostanin.org/2014/02/11/playing-with-mac-os-x-on-kvm/) which
works like a charm, except for the final part where I am supposed to
install a bootloader (Chimera, Chameleon) to be able to boot my virtual
machine. In pr
Hi folks,
I am looking for feedback regarding work-in-progress or planned CPU power
management features for Qemu-KVM based Virtual Machines.
Looking back through the mailing list archives I did not find any discussion
or patches relating to the general problem of virtual machine power
management.
On Thu, Nov 06, 2014 at 01:53:35PM +0100, Max Reitz wrote:
> On 2014-11-06 at 13:26, Markus Armbruster wrote:
> >Max Reitz writes:
> >
> >>On 2014-11-04 at 19:45, Markus Armbruster wrote:
> >>>I'll try to explain all solutions fairly. Isn't easy when you're as
> >>>biased towards one of them as I
On 2014-11-06 at 15:56, Jeff Cody wrote:
On Thu, Nov 06, 2014 at 01:53:35PM +0100, Max Reitz wrote:
On 2014-11-06 at 13:26, Markus Armbruster wrote:
Max Reitz writes:
On 2014-11-04 at 19:45, Markus Armbruster wrote:
I'll try to explain all solutions fairly. Isn't easy when you're as
biased
On Thu, Nov 06, 2014 at 02:37:54PM +0800, Amos Kong wrote:
> On Wed, Nov 05, 2014 at 09:47:47AM +0100, Gerd Hoffmann wrote:
> > On Mi, 2014-11-05 at 00:49 +0800, Amos Kong wrote:
> > > qemu_input_find_handler() prefers a handler associated with con.
> > > But if none exists, it takes any. This patc
Am 06.11.2014 um 14:57 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Am 04.11.2014 um 19:45 hat Markus Armbruster geschrieben:
> >> I'll try to explain all solutions fairly. Isn't easy when you're as
> >> biased towards one of them as I am. Please bear with me.
> >>
> >>
> >>
Christopher Covington writes:
> Hi,
>
> [snip--for full message see
> https://groups.google.com/d/msg/android-emulator-dev/dltBnUW_HzU/2tSZNLaVzmQJ]
>
>> 5) Relationship with upstream
>>
>> In an ideal world, we would not need a fork, and all code would live on
>> the upstream QEMU git.
>>
>> I
No one uses the 'node' field any more, so remove it
from 'struct qemu_laiocb', and this can save 16byte
for the struct on 64bit arch.
Signed-off-by: Ming Lei
---
block/linux-aio.c |1 -
1 file changed, 1 deletion(-)
diff --git a/block/linux-aio.c b/block/linux-aio.c
index f5ca41d..b12da25 1
The 1st patch fixes batch submission.
The 2nd one fixes -EAGAIN for non-batch case.
The 3rd one is a cleanup.
This patchset is splitted from previous patchset(dataplane: optimization
and multi virtqueue support), as suggested by Stefan.
v3:
- rebase on QEMU master
v2:
- code sty
In the enqueue path, we can't complete request, otherwise
"Co-routine re-entered recursively" may be caused, so this
patch fixes the issue with below ideas:
- for -EAGAIN or partial completion, retry the submision by
schedule an BH in following completion cb
- for part of c
Previously -EAGAIN is simply ignored for !s->io_q.plugged case,
and sometimes it is easy to cause -EIO to VM, such as NVME device.
This patch handles -EAGAIN by io queue for !s->io_q.plugged case,
and it will be retried in following aio completion cb.
Suggested-by: Paolo Bonzini
Signed-off-by: M
Hello Damien,
On Thu, Nov 6, 2014 at 8:38 AM, Damien Hilloulin
wrote:
> Hello everyone,
>
> I'm a newcomer in QEMU and my goal would be to port an existing system
> simulator using another emulator to QEMU.
> Some work has already been done, and Sparc has been the main target so far
> because of
On Thu, 6 Nov 2014, Xu, Quan wrote:
> > -Original Message-
> > From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> > Sent: Monday, November 03, 2014 7:54 PM
> > To: Xu, Quan
> > Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org;
> > stefano.stabell...@eu.citrix.com
> > Sub
* Li Liang (liang.z...@intel.com) wrote:
> Instead of sending the guest memory directly, this solution compress
> the ram page before sending, after receiving, the data will be
> decompressed.
> This feature can help to reduce the data transferred about
> 60%, this is very useful when the network b
> -Original Message-
> From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> Sent: Thursday, November 06, 2014 11:42 PM
> To: Xu, Quan
> Cc: Stefano Stabellini; qemu-devel@nongnu.org; xen-de...@lists.xen.org
> Subject: RE: [PATCH 2/4] Qemu-Xen-vTPM: Register Xen stubdom vTP
On 6 November 2014 14:49, Eduardo Otubo wrote:
> Right now seccomp is breaking the compilation of Qemu on armv7l due
> to libsecomp current lack of support for this arch. This problem is
> already fixed on libseccomp upstream but no release date for that is
> scheduled to far. This patch disables
This patch extends arm_excp_unmasked() to use lookup tables for determining
whether IRQ and FIQ exceptions are masked. The lookup tables are based on the
ARMv8 and ARMv7 specification physical interrupt masking tables.
If EL3 is using AArch64 IRQ/FIQ masking is ignored in all exception levels
oth
Adds a dedicated function and a lookup table for determining the target
exception level of IRQ and FIQ exceptions. The lookup table is taken from the
ARMv7 and ARMv8 specification exception routing tables.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
v8 -> v9
- Fixed target_el_t
Version 10 of the ARM processor security extension (TrustZone) support. This
patchset includes changes to support the processor security extensions
on ARMv7 aarch32 with hooks for later enabling v8 aarch64/32.
This is a rebase of v9 to a more recent master as well as a fix for an
overlooked bug i
From: Fabian Aggeler
Adds secure and non-secure bank register suport for TTBCR.
Added new struct to compartmentalize the TCR data and masks. Removed old
tcr/ttbcr data and added a 4 element array of the new structs in cp15. This
allows for one entry per EL. Added a CP register definition for T
From: Fabian Aggeler
If EL3 is in AArch32 state certain cp registers are banked (secure and
non-secure instance). When reading or writing to coprocessor registers
the following macros can be used.
- A32_BANKED macros are used for choosing the banked register based on provided
input security ar
From: Fabian Aggeler
Define a new ARM CP register info list for the ARMv7 Security Extension
feature. Register that list only for ARM cores with Security Extension/EL3
support. Moving AArch32 SCR into Security Extension register group.
Signed-off-by: Sergey Fedorov
Signed-off-by: Fabian Aggeler
From: Fabian Aggeler
Prepare ARMCPRegInfo to support specifying two fieldoffsets per
register definition. This will allow us to keep one register
definition for banked registers (different offsets for secure/
non-secure world).
Also added secure state tracking field and flags. This allows for
i
Added additional NS-bit to CPREG hash encoding. Updated hash lookup
locations to specify hash bit currently set to non-secure.
Signed-off-by: Greg Bellows
---
v8 -> v9
- Fixed CP_REG_NS_MASK
- Changed ENCODE_CP_REG argument order so ns follows is64
- Replaced use of CP_REG_NS_MASK with CP_REG_
From: Fabian Aggeler
When EL3 is running in AArch32 (or ARMv7 with Security Extensions)
FCSEIDR, CONTEXTIDR, TPIDRURW, TPIDRURO and TPIDRPRW have a secure
and a non-secure instance.
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
---
v8 -> v9
- Changed contextidr structure definiti
From: Fabian Aggeler
Prepare for cp register banking by inserting every cp register twice,
once for secure world and once for non-secure world.
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
---
v8 -> v9
- Fixed setting of secure field in add_cpreg_to_hashtable so it uses secstate
From: Fabian Aggeler
SCR.{IRQ/FIQ} bits allow to route IRQ/FIQ exceptions to monitor CPU
mode. When taking IRQ exception to monitor mode FIQ exception is
additionally masked.
Signed-off-by: Sergey Fedorov
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
--
From: Fabian Aggeler
Use MVBAR register as exception vector base address for
exceptions taken to CPU monitor mode.
Signed-off-by: Sergey Fedorov
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
v8 -> v9
- Fixed declaration order of the MVBARR registe
From: Fabian Aggeler
Implements NSACR register with corresponding read/write functions
for ARMv7 and ARMv8.
Signed-off-by: Sergey Fedorov
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
v8 -> v9
- Removed unused NSACR constants
- Added TODO for trap
From: Fabian Aggeler
Set ARM_FEATURE_EL3 feature for CPUs that implement Security Extensions.
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
---
target-arm/cpu.c | 4
1 file changed, 4 insertions(+)
diff --git a/target-arm/cpu.c b/target-arm/cpu.c
index d3db279..1871865 10064
1 - 100 of 163 matches
Mail list logo
