From: Alexander Graf
This patch adds all the prerequisites for AArch64 support that didn't
fit into split up patches. It extends important bits in the core cpu
headers to also take AArch64 mode into account.
Add new ARM_TBFLAG_AARCH64_STATE translation buffer flag
indicate an ARMv8 cpu running i
From: Alexander Graf
The cpu_env tcg variable will be used by both the AArch32 and AArch64
handling code. Unstaticify it, so that both sides can make use of it.
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
Changes in v3:
- None because consensus alternative to non static arm cp
Resend of v3 with part 6 removed and change notes included.
Alexander Graf (10):
ARM: Export cpu_env
ARM: Prepare translation for AArch64 code
ARM: Add AArch64 translation stub
AArch64: Add gdb stub
linux-user: Don't treat aarch64 cpu names specially
linux-user: Add syscall handling fo
On 05/11/13 00:45, Michael Roth wrote:
> These patches apply on top of qemu.git master, and can also be obtained from:
> git://github.com/mdroth/qemu.git qapi-native-lists
>
> Sending this now since a number of series have popped up in the past that
> wanted this, and Amos has some pending patches
From: Alexander Graf
If we want to compile a target machine type that is AArch64 capable,
we need to add a new 64-bit capable ARM target. Use AArch64 since that
is the official ARM LTD name.
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
configure| 8
lin
From: Alexander Graf
This patch adds support for AArch64 in all the small corners of
linux-user and beyond.
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
default-configs/aarch64-linux-user.mak | 3 +
linux-user/aarch64/syscall.h | 37 ++
linux-user/aarch64/targe
ignore this part 6/12 one, somehow I neglected to remove it from the series
the fix in 12/12 is the one riku recommended
From: Alexander Graf
The AArch64 syscall definitions are all publicly available in the Linux
kernel. Let's add them to our linux-user emulation target, so that we
can easily handle AArch64 syscalls.
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
linux-user/aarch64/syscall_nr.h |
From: Alexander Graf
32-bit ARM has a lot of different names for different types of CPUs it supports.
On AArch64, we don't have this, so we really don't want to execute the 32-bit
logic. Stub it out for AArch64 linux-user guests.
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
lin
From: Alexander Graf
Glibc 1.17 checks for the host kernel version on startup. Unfortunately,
it also checks whether the host kernel version is recent enough for the
target to run at all.
Since AArch64 support only got introduced in 3.8.0, that means that glibc
refuses to run on any older kernel
From: Alexander Graf
We want to be able to debug AArch64 guests. So let's add the respective gdb
stub functions and xml descriptions that allow us to do so.
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
gdb-xml/aarch64-core.xml | 46 ++
gdb-xml/aarch64-fp
From: Andreas Schwab
This patch adds signal handling for AArch64. The code is based on the
respective source in the Linux kernel.
Signed-off-by: Andreas Schwab
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
linux-user/arm/target_signal.h | 4 +
linux-user/signal.c|
From: Alexander Graf
Glibc 1.17 checks for the host kernel version on startup. Unfortunately,
it also checks whether the host kernel version is recent enough for the
target to run at all.
Since AArch64 support only got introduced in 3.8.0, that means that glibc
refuses to run on any older kernel
From: Alexander Graf
This patch adds all the prerequisites for AArch64 support that didn't
fit into split up patches. It extends important bits in the core cpu
headers to also take AArch64 mode into account.
Add new ARM_TBFLAG_AARCH64_STATE translation buffer flag
indicate an ARMv8 cpu running i
From: Alexander Graf
Some syscall handlers have special code for ARM enabled that we don't
need on AArch64. Exclude AArch64 in those cases. In other places we
can share struct definitions with other targets or have to provide our
own.
With this patch applied, most syscall definitions in linux-us
From: Alexander Graf
We should translate AArch64 mode separately from AArch32 mode. In AArch64 mode,
registers look vastly different, instruction encoding is completely different,
basically the system turns into a different machine.
So let's do a simple if() in translate.c to decide whether we c
From: Alexander Graf
The cpu_env tcg variable will be used by both the AArch32 and AArch64
handling code. Unstaticify it, so that both sides can make use of it.
Signed-off-by: Alexander Graf
Signed-off-by: John Rigby
---
target-arm/translate.c | 2 +-
target-arm/translate.h | 2 ++
2 files ch
Version 3 of series to add Aarch64 support.
Alexander Graf (11):
ARM: Export cpu_env
ARM: Prepare translation for AArch64 code
ARM: Add AArch64 translation stub
AArch64: Add gdb stub
linux-user: Don't treat aarch64 cpu names specially
linux-user: AArch64 requires at least 3.8.0
linux
On Tue, Apr 09, 2013 at 05:43:43PM +0200, Paolo Bonzini wrote:
> Using qemu_memalign only leaves the RAM zero by chance, because libc
> will usually use mmap to satisfy our huge requests. But memory will
> not be zero when using MALLOC_PERTURB_ with a nonzero value. In the
> case of incoming migr
Am 08.05.2013 06:39, schrieb qiaonuo...@cn.fujitsu.com:
> From: Qiao Nuohan
>
> This patch is used to remove twice include of "qemu-common.h" in
> block/win32-aio.c
>
> Signed-off-by: Qiao Nuohan
> ---
> block/win32-aio.c |1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --gi
cc qemu-trivial
Thanks for the patch.
Regards,
Peter
On Wed, May 8, 2013 at 2:39 PM, wrote:
> From: Qiao Nuohan
>
> This patch is used to remove twice include of "qemu-common.h" in
> block/win32-aio.c
>
> Signed-off-by: Qiao Nuohan
> ---
> block/win32-aio.c |1 -
> 1 files changed, 0 in
From: Qiao Nuohan
This patch is used to remove twice include of "qemu-common.h" in
block/win32-aio.c
Signed-off-by: Qiao Nuohan
---
block/win32-aio.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/block/win32-aio.c b/block/win32-aio.c
index 5d0fbbf..fcb7c75 100644
---
Public bug reported:
As discussed in maillist: http://lists.nongnu.org/archive/html/qemu-
devel/2013-04/msg03582.html
[this problem still existed in latest qemu.git]
qemu -device virtio-net-pci,netdev=ndev1,id=id1 -netdev tap,id=ndev1 \
-device e1000,netdev=ndev2,id=id2 -netdev ta
USB_DEV_FLAG_IS_HOST is the bit number, not value. Booting with a
"Fitbit Base Station" USB dongle was triggering this assert.
Signed-off-by: Michael Marineau
---
hw/usb/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/usb/core.c b/hw/usb/core.c
index 15a150a..05948c
First, having a single qcow2 file open for read-write access by more
than one process in unsupported.
Second, this version of qemu/kvm is too old to be supported upstream,
it's a few years old already and there has been *lots* of changes since
that version.
** Changed in: qemu
Status: New
From: Liu Ping Fan
Each address space listener has PhysPageMap *cur_map, *next_map,
the switch from cur_map to next_map complete the RCU style. The
mem_commit() do the switch, and it is against reader but AddressSpace's
lock or later RCU mechanism (around address_space_translate() ).
Signed-off-
From: Liu Ping Fan
Now, each AddressSpaceDispatch has its own radix-tree, and all of them
lie on phys_section[] and phys_map_nodes[]. When we want lockless
mmio dispatch, we need something like RCU.
Acheive this with PhysPageTable which contains all of the info for all
radix trees. After all add
From: Liu Ping Fan
This is an old idea, I post last year,
http://permalink.gmane.org/gmane.comp.emulators.qemu/164845
I rebase it, after Paolo's [PATCH 00/40] Memory-related changes sneak peek for
1.6
(Paolo's tree git://github.com/bonzini/qemu.git, branch iommu.)
Open issue--the dependency
From: Qiao Nuohan
When calling create_header, create_dump_bitmap and create_pages, some memory
spaces
are allocated. The following patch will use this function to free these spaces.
Signed-off-by: Qiao Nuohan
Reviewed-by: Zhang Xiaohe
---
dump.c | 19 +++
1 files changed, 1
From: Qiao Nuohan
Add API to create header, sub header of vmcore in kdump-compressed format.
The data is store in struct DumpState.
The following patch will use this function to gather data of header, then
write them into vmcore.
Signed-off-by: Qiao Nuohan
Reviewed-by: Zhang Xiaohe
---
dump.
From: Qiao Nuohan
Add API to get data of the 1st and 2nd dump bitmap and save them into tmp files.
The following patch will use these functions to gather data of dump bitmap,
then write them into vmcore.
Signed-off-by: Qiao Nuohan
Reviewed-by: Zhang Xiaohe
---
dump.c| 98 +++
From: Qiao Nuohan
Make monitor command 'dump-guest-memory' dump in kdump-compressed format.
The command's usage:
dump [-p] protocol [begin] [length] [format]
'format' is used to specified the format of vmcore and can be:
1. 'elf': ELF format, without compression
2. 'zlib': kdump-compressed form
From: Qiao Nuohan
The following patch will use these functions to write cached data into vmcore.
Header is cached in DumpState, and bitmap and page are cached in tmp files.
Signed-off-by: Qiao Nuohan
Reviewed-by: Zhang Xiaohe
---
dump.c| 259 ++
From: Qiao Nuohan
Add API to get data of page desc and page data and save them into tmp files.
The following patch will use these functions to gather data of page desc and
page data, then write them into vmcore
Signed-off-by: Qiao Nuohan
Reviewed-by: Zhang Xiaohe
---
dump.c|
From: Qiao Nuohan
Struct dump_bitmap is associated with a tmp file, and the tmp file can be used
to save data of bitmap in kdump-compressed format temporarily.
The following patch will use these functions to get the data of bitmap and cache
them into tmp files.
Signed-off-by: Qiao Nuohan
Review
From: Qiao Nuohan
Move includes and definition of struct DumpState into include/sysemu/dump.h.
Signed-off-by: Qiao Nuohan
Reviewed-by: Zhang Xiaohe
---
dump.c| 29 -
include/sysemu/dump.h | 30 ++
2 files changed, 30
From: Qiao Nuohan
Struct dump_bitmap is associated with a tmp file, and the tmp file can be used
to save data of page desc and page data in kdump-compressed format temporarily.
The following patch will use these function to get the data of page desc and
page data and cache them in tmp files.
Sig
From: Qiao Nuohan
Hi, all
The last version is here:
http://lists.gnu.org/archive/html/qemu-devel/2013-05/msg00803.html
Command 'dump-guest-memory' was introduced to dump guest's memory. But the
vmcore's format is only elf32 or elf64. The message is here:
http://lists.gnu.org/archive/html/qemu-d
Sorry, the cc list is wrong, I will resend the mails.
> -Original Message-
> From: qiaonuo...@cn.fujitsu.com [mailto:qiaonuo...@cn.fujitsu.com]
> Sent: Wednesday, May 08, 2013 9:54 AM
> To: qemu-devel@nongnu.org
> Cc:
> ebl...@redhat.com.berra...@redhat.com.afaer...@suse.de.d.hatayama@jp.fu
From: Petar Jovanovic
This is a small follow-up change to "fix incorrect behaviour for INSV".
It includes two minor modifications:
- sizefilter is constant so it can be moved inside of the block,
- several lines of the code are replaced with a call to deposit64.
No functional change.
Signed-o
True. Nice catch. This will simplify this section even more.
I will send an updated patch with this change included.
Petar
From: Peter Maydell [peter.mayd...@linaro.org]
Sent: Thursday, May 09, 2013 7:54 PM
To: Petar Jovanovic
Cc: qemu-devel@nongnu.org; Pet
On 13-05-12 05:14 PM, Michael Tokarev wrote:
> First, having a single qcow2 file open for read-write access by more
> than one process in unsupported.
But I don't, if I understand how qcow2 snapshots work. Let me apologize
if I was not clear. Each of the VMs have their own snapshot of the
common
And the same QEMU/kernel/image works fine on a Linux host?
If you can provide the files I need to reproduce I might be able to take
a look at it. (If it did the same thing on linux host that would be
higher priority for me, so if you can cross-check that would be
helpful.)
--
You received this b
Adding to the lot, from the same gdb session.
(gdb) frame 3
#3 0x5664fe06 in ide_trim_bh_cb (opaque=0x57282c28) at hw/ide/core.c:360
360 iocb->common.cb(iocb->common.opaque, iocb->ret);
(gdb) l
355
356 static void ide_trim_bh_cb(void *opaque)
357 {
358 TrimAIOCB *ioc
Il 10/05/2013 17:11, Anthony Liguori ha scritto:
> Chegu Vinod writes:
>
>> On 5/10/2013 6:07 AM, Anthony Liguori wrote:
>>> Chegu Vinod writes:
>>>
If a user chooses to turn on the auto-converge migration capability
these changes detect the lack of convergence and throttle down th
Hi Peter,
Thanks, that made an improvement. Now I'm just stuck in a loop of the
kernel resetting the scsi bus :)
(see attachment)
** Attachment added: "Endless resets"
https://bugs.launchpad.net/qemu/+bug/1094564/+attachment/3674705/+files/Screen%20Shot%202013-05-12%20at%2012.38.33%20PM.png
Am 10.05.2013 22:09, schrieb mdroth:
> On Fri, May 10, 2013 at 09:53:27PM +0200, Laszlo Ersek wrote:
>> On 05/10/13 21:30, mdroth wrote:
>>> On Wed, May 08, 2013 at 05:31:34PM +0200, Laszlo Ersek wrote:
I should have paid more attention to portability and error path cleanup
in the CVE-201
I managed to capture a little more info about this bug by passing -drive
file='myharddrive.img'. The kernel panic is happening in the sym53c8xx
driver. See the attached screenshot for detail.
I can also attach the kernel that I'm using if needed. Just let me know.
** Attachment added: "Kernel pa
I suspect this may be because we were defaulting to a broken coroutine
backend (a bug fixed with commit 7c2acc7). Can you retry with the
current 1.5 release candidate? (source download available at
http://wiki.qemu.org/Download)
--
You received this bug notification because you are a member of qe
Hi,
Now QEMU has a guest agent tool:
http://wiki.qemu.org/Features/QAPI/GuestAgent
Guest agent is used to send "guest agent commands" to agent, and agent
will do some work and return the results via QMP protocol. Now
qemu-guest-agent is mainly for single direction: Host->Guest, that is
users
Public bug reported:
On CentOS-6.4.latest, I am trying to run several KVM VMs with snapshots
of a single qcow2 image. Randomly some VMs will crash though. There's
a downstream bug report at http://bugs.centos.org/view.php?id=6441 and
included in that is an "abrt" crash report that contains the f
** Changed in: qemu (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1179104
Title:
client crash during debian ppc installation
Status in QEMU:
Confirme
I duplicated this as well. I tried both the qemu-system-arm available in
macports and also from homebrew with the same results. Host system is
also 10.8 "mountain lion".
My boot command: qemu-system-arm -kernel kernel/zImage -cpu arm1176 -m
256 -M versatilepb -no-reboot -serial stdio -append "root
** Changed in: qemu
Status: New => Confirmed
** Bug watch added: Debian Bug tracker #707732
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707732
** Also affects: qemu (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707732
Importance: Unknown
Status: Unknown
This looks like some TRIM (mis)support in action. It crashes in
different paces but repeatable/reproducible (ie, it crash with different
error on my system, but the error is always the same on my system).
Running it under gdb:
(gdb) ru -m 256 -hda /stage/tmp/mjt/tmp/ppc.img -cdrom
/stage/tmp/mjt
On 12 May 2013 13:55, Jean-Christophe DUBOIS wrote:
> In your opinion, is this patch set good enough in its actual state for
> inclusion?
>
> Are you expecting anything else from me (beside maybe adding more i.MX
> devices in the future)?
I haven't looked at this series yet because we're in codef
Peter (and all),
In your opinion, is this patch set good enough in its actual state for
inclusion?
Are you expecting anything else from me (beside maybe adding more i.MX
devices in the future)?
Thanks
JC
On 05/08/2013 10:28 AM, Jean-Christophe DUBOIS wrote:
This series of patches add the
On Tue, May 07, 2013 at 01:53:03AM +, Zhanghaoyu (A) wrote:
> >> >> With regard to old version linux guest(e.g., rhel-5.5), in ISR
> >> >> processing, mask and unmask msi-x vector every time, which result in
> >> >> VMEXIT, then QEMU will invoke kvm_irqchip_update_msi_route() to ask KVM
> >>
On Fri, May 10, 2013 at 02:40:04PM +0200, Jan Kiszka wrote:
> On 2013-05-09 18:35, Alex Williamson wrote:
> > I posted these about 6 months ago and Jan felt we should implement
> > MSI notifiers like we have for MSI-X. That still hasn't happened.
>
> Device assignments are the only currently know
Makes it easier to debug situations where the source and target have
different ram blocks in a device and migration fails due to that, for
instance a BAR size change on a PCI device.
Signed-off-by: Alon Levy
---
v3: use RAM_ADDR_FMT
arch_init.c | 3 +++
1 file changed, 3 insertions(+)
diff --g
looks like it also happens in 1.5.0-rc1, will check later with git
bisect in the latest git release based on rc1.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1176366
Title:
TCPIP not working on q
On Thu, May 09, 2013 at 10:36:05AM -0600, Alex Williamson wrote:
> Track the last MSIMessage programmed so we can determine when it has
> changed and update the routing to the guest.
>
> Signed-off-by: Alex Williamson
> ---
> hw/i386/kvm/pci-assign.c | 27 +++
> 1 file
On Mon, May 06, 2013 at 01:00:09PM +0300, Michael S. Tsirkin wrote:
> On Mon, May 06, 2013 at 02:52:37AM +, Zhanghaoyu (A) wrote:
> > >> With regard to old version linux guest(e.g., rhel-5.5), in ISR
> > >> processing, mask and unmask msi-x vector every time, which result in
> > >> VMEXIT, th
12.05.2013 13:32, Michael Tokarev wrote:
[]
> The following changes since commit 38ebb396c955ceb2ef7e246248ceb7f8bfe1b774:
>
> target-i386: ROR r8/r16 imm instruction fix (2013-05-10 19:59:54 +0200)
>
> are available in the git repository at:
>
> git://git.corpit.ru/qemu.git trivial-patches-
Here goes the official pull request for the trivial patch queue
for qemu 1.5 release. I already sent a smaller pull request
when 1.5-rc0 has been tagged, but that one went unanswered.
So the next pull request includes patches previously sent.
This series contains just the trivial stuff, with the
Il 10/05/2013 23:41, Jordan Justen ha scritto:
> The isapc machine with seabios currently requires the BIOS region
> to be read/write memory rather than read-only memory.
>
> KVM currently cannot support the BIOS as a ROM region, but qemu
> in non-KVM mode can. Based on this, isapc machine current
Am 10.05.2013 21:58, schrieb Igor Mitsyanko:
> sys/types.h is taken out from "ifdef __OpenBSD__" guard. It should be
> safe for other systems, according to following survey:
> http://hacks.owlfolio.org/header-survey/
>
> This fixes build for CONFIG_IOVEC-less systems (mingw).
>
> Signed-off-by: Igo
10.05.2013 23:58, Igor Mitsyanko wrote:
> sys/types.h is taken out from "ifdef __OpenBSD__" guard. It should be
> safe for other systems, according to following survey:
> http://hacks.owlfolio.org/header-survey/
>
> This fixes build for CONFIG_IOVEC-less systems (mingw).
Thanks, applied to the tr
68 matches
Mail list logo
