Some code in qcow2-snapshot.c directly accesses bs->file, so in those
places errors can't be injected by other events. Since the code in
qcow2-snapshot.c is similar to the other qcow2 internal code (in regards
to e.g. the L1 table), add some debug events.
Signed-off-by: Wenchao Xia
Reviewed-by: M
Signed-off-by: Wenchao Xia
Reviewed-by: Max Reitz
---
block/qcow2-snapshot.c | 25 +
1 files changed, 21 insertions(+), 4 deletions(-)
diff --git a/block/qcow2-snapshot.c b/block/qcow2-snapshot.c
index 70e329e..685ef8b 100644
--- a/block/qcow2-snapshot.c
+++ b/block/qc
V2:
1: all fail case will goto fail section.
2: add the goto code.
v3:
Address Stefan's comments:
2: don't goto fail after allocation failure.
3: use sn->l1size correctly in qcow2_free_cluster().
4-7: add test case to verify the error paths.
Other:
1: new patch fix a existing bug,
From: Peter Crosthwaite
Fix the name stem of the devicetree API (P1 - s/qemu_devtree/qemu_fdt)
and cleanup error report (P3). Trivial patch P2 fixing an arugment name
along the way.
Tested using:
1: Alex's e500 test vector.
2: Xilinx Zynq (tests arm/boot.c).
I have testing using Zynq with Mem
From: Peter Crosthwaite
The qemu_devtree API is a wrapper around the fdt_ set of APIs.
Rename accordingly.
Signed-off-by: Peter Crosthwaite
---
device_tree.c| 62 ++---
hw/arm/boot.c| 24 ++---
hw/arm/vexpress.c| 18 ++--
hw/microblaze/bo
From: Peter Crosthwaite
Looking at the implementation, this doesn't really have a lot to do
with arrays. Its just a pointer to a buffer and is passed through
to the wrapped fn (qemu_fdt_setprop) unchanged. So rename to make it
consistent with libfdt, which in the wrapped function just calls it
"v
From: Peter Crosthwaite
There are a mix of usages of the qemu_fdt_* API calls, some which
wish to assert and abort QEMU on failure and some of which wish to do
their own error handling. The latter in more correct, but the former
is in the majority and more pragmatic. However the asserting clients
On Fr, 2013-11-08 at 17:51 +0100, Jan Kiszka wrote:
> On 2013-11-08 16:39, Gerd Hoffmann wrote:
> > Hi,
> >
> >> OK, then here is the first issue I ran into while trying libusbx (git
> >> head, i.e. 1.0.17+: The new stack causes significant latency issues that
> >> makes it almost unusable for p
On So, 2013-11-10 at 19:25 +0100, Stefan Weil wrote:
> Hello Gerd,
>
> could you please install bison and flex on the buildbot machine for
> default_mingw?
Done.
cheers,
Gerd
On Sun, 10 Nov 2013 12:36:29 +0200
"Michael S. Tsirkin" wrote:
> On Fri, Nov 08, 2013 at 06:33:12PM +0100, Igor Mammedov wrote:
> > On Fri, 8 Nov 2013 12:22:12 +0200
> > Vasilis Liaskovitis wrote:
> >
> > > Hi,
> > >
> > > On Thu, Nov 07, 2013 at 03:03:42PM +0200, Michael S. Tsirkin wrote:
> >
On Sun, Nov 10, 2013 at 05:07:03PM +0100, Stefan Weil wrote:
> could you please have a look at these buildbots (maybe others, too):
>
> xen_i386_debian_6_0
> xen_x86_64_debian_6_0
>
> Both fail during the configuration:
>
> ERROR: unknown option --disable-debug-info
fetching branch xen-next fro
On Mon, Nov 11, 2013 at 2:02 PM, Anthony Liguori wrote:
> On Sun, Nov 10, 2013 at 3:15 PM, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> I've ported the SDL1.2 code over, and rewritten it to use the SDL2 interface.
>>
>> The biggest changes were in the input handling, where SDL2 has done a major
On So, 2013-11-10 at 15:58 +0100, Stefan Weil wrote:
> The local function console_print_text_attributes is no longer used
> since
> commit 7d6ba01c3741bc32ae252bf64a5fd3f930c2df4f.
Reviewed-by: Gerd Hoffmann
cheers,
Gerd
On So, 2013-11-10 at 16:04 +0100, Stefan Weil wrote:
> +console_putchar_csi(int esc_param0, int esc_param1, int ch, int
> nb_esc_params) "escape sequence CSI%d;%d%c, %d parameters"
> +console_putchar_unhandled(int ch) "unhandled escape character '%c'"
Reviewed-by: Gerd Hoffmann
cheers,
Gerd
On Fri, Nov 08, 2013 at 10:52:09AM -0500, Gabriel L. Somlo wrote:
> On Fri, Nov 08, 2013 at 02:39:25PM +0100, Stefan Hajnoczi wrote:
> > On Fri, Nov 08, 2013 at 12:12:52AM +0100, Alexander Graf wrote:
> >> We can easily modify SeaBIOS to just loop through all PCI devices,
> >> look for an e1000 and
On Fri, Nov 08, 2013 at 11:26:49AM +0800, Fam Zheng wrote:
> If backing file doesn't exist, the error message is confusing and
> misleading:
>
> $ qemu /tmp/a.qcow2
> qemu: could not open disk image /tmp/a.qcow2: Could not open file: No
> such file or directory
>
> But...
>
> $ l
2013/11/5 Stefan Hajnoczi :
> On Mon, Nov 04, 2013 at 11:28:41AM +0100, Matthias Brugger wrote:
>> v2:
>> - fix issues found by checkpatch.pl
>> - change the descritpion of patch 3
>>
>> This patch series makes the thread pool implementation modular.
>> This allows each drive to use a special imp
Il 10/11/2013 11:31, Michael S. Tsirkin ha scritto:
> > Reported-by: Luiz Capitulino
> > Signed-off-by: Paolo Bonzini
>
> So this causes a 12% performance regression on some TCG
> tests, I think we should look into a smarter
> datastructure to solve the issues.
It causes a 12% performance regre
On Mon, Nov 04, 2013 at 11:55:47AM +0100, Paolo Bonzini wrote:
> Il 04/11/2013 11:47, Fam Zheng ha scritto:
> >>>
> >>> -void bdrv_set_dirty_tracking(BlockDriverState *bs, int granularity);
> >>> -int bdrv_get_dirty(BlockDriverState *bs, int64_t sector);
> >>> +typedef struct BdrvDirtyBitmap BdrvDi
On Mon, Nov 04, 2013 at 05:30:10PM +0800, Fam Zheng wrote:
> @@ -2785,9 +2792,7 @@ static int coroutine_fn
> bdrv_co_do_writev(BlockDriverState *bs,
> ret = bdrv_co_flush(bs);
> }
>
> -if (bs->dirty_bitmap) {
> bdrv_set_dirty(bs, sector_num, nb_sectors);
> -}
Forg
On Mon, Nov 04, 2013 at 05:30:10PM +0800, Fam Zheng wrote:
> Previously a BlockDriverState has only one dirty bitmap, so only one
> caller (e.g. a block job) can keep track of writing. This changes the
> dirty bitmap to a list and creates a BdrvDirtyBitmap for each caller, the
> lifecycle is manage
Il 11/11/2013 10:10, Dave Airlie ha scritto:
>> > It's very hard to review ATM due to the split.
> No I talked to enough people at kvmforum and everyone said I should
> split this into a separate file, please don't make me undo that now, I
> originally did it with ifdefs and just spent a few days r
Am 11.11.2013 08:44, schrieb Alexey Kardashevskiy:
> This adds a macro to calculate the highest bit set.
Isn't that already available as ffs / clz GCC builtin with wrapper in
qemu/bitops.h? What's the difference to your macro? CC'ing Paolo.
Andreas
> If used on constant
> values, no code will be
On 11/11/2013 10:57 PM, Andreas Färber wrote:
> Am 11.11.2013 08:44, schrieb Alexey Kardashevskiy:
>> This adds a macro to calculate the highest bit set.
>
> Isn't that already available as ffs / clz GCC builtin with wrapper in
> qemu/bitops.h? What's the difference to your macro? CC'ing Paolo.
>
Am 04.11.2013 um 11:28 hat Matthias Brugger geschrieben:
> This patch introduces function pointers for the thread pool, so that
> it's implementation can be set at run-time.
>
> Signed-off-by: Matthias Brugger
Like Stefan said, this can really only be given a meaningful review in
context with an
Am 04.11.2013 um 11:28 hat Matthias Brugger geschrieben:
> This patch allows to choose at the command line level which thread pool
> implementation will be used by every block device.
>
> Signed-off-by: Matthias Brugger
This would require a change to blockdev-add in qapi-schema.json in order
to
Am 11.11.2013 08:44, schrieb Alexey Kardashevskiy:
> This converts +foo/-foo to "foo=on"/"foo=off" respectively when
> QEMU parser is used for the command line options.
>
> "-cpu" parsers in x86 and other architectures should be unaffected
> by this change.
>
> Signed-off-by: Alexey Kardashevskiy
On Mon, Nov 11, 2013 at 11:00:45AM +0100, Matthias Brugger wrote:
> 2013/11/5 Stefan Hajnoczi :
> > I'd also like to see the thread pool implementation you wish to add
> > before we add a layer of indirection which has no users yet.
>
> Fair enough, I will evaluate if it will make more sense to im
On 2013-11-11 13:41, Andreas Färber wrote:
> Am 11.11.2013 08:44, schrieb Alexey Kardashevskiy:
>> This converts +foo/-foo to "foo=on"/"foo=off" respectively when
>> QEMU parser is used for the command line options.
>>
>> "-cpu" parsers in x86 and other architectures should be unaffected
>> by this
Am 24.10.2013 um 12:06 hat Peter Lieven geschrieben:
> Reviewed-by: Eric Blake
> Signed-off-by: Peter Lieven
> ---
> block.c | 37 -
> 1 file changed, 36 insertions(+), 1 deletion(-)
>
> diff --git a/block.c b/block.c
> index 0c0b0ac..b28dd42 100644
> --- a
Am 11.11.2013 13:52, schrieb Jan Kiszka:
> On 2013-11-11 13:41, Andreas Färber wrote:
>> Am 11.11.2013 08:44, schrieb Alexey Kardashevskiy:
>>> This converts +foo/-foo to "foo=on"/"foo=off" respectively when
>>> QEMU parser is used for the command line options.
>>>
>>> "-cpu" parsers in x86 and oth
Am 11.11.2013 08:44, schrieb Alexey Kardashevskiy:
> This patch is to demonstrate a static property handling in PowerPC.
> Running QEMU with -cpu host,-vsx disables VSX bit in
> PowerPCCPU::env::flags.
>
> Signed-off-by: Alexey Kardashevskiy
> ---
> target-ppc/translate_init.c | 7 +++
> 1 f
If an explicit driver option is present, but doesn't specify a valid
driver, then bdrv_open() should fail instead of probing the format.
Signed-off-by: Kevin Wolf
---
block.c| 5 +
tests/qemu-iotests/051 | 7 +++
tests/qemu-iotests/051.out | 9 +
3 files c
On Nov 11, 2013 1:10 AM, "Dave Airlie" wrote:
>
> On Mon, Nov 11, 2013 at 2:02 PM, Anthony Liguori
wrote:
> > On Sun, Nov 10, 2013 at 3:15 PM, Dave Airlie wrote:
> >> From: Dave Airlie
> >>
> >> I've ported the SDL1.2 code over, and rewritten it to use the SDL2
interface.
> >>
> >> The biggest
On Mon, Nov 11, 2013 at 02:54:59PM +0100, Kevin Wolf wrote:
> If an explicit driver option is present, but doesn't specify a valid
> driver, then bdrv_open() should fail instead of probing the format.
>
> Signed-off-by: Kevin Wolf
> ---
> block.c| 5 +
> tests/qemu-iotest
On Mon, 11 Nov 2013 13:41:05 +0100
Andreas Färber wrote:
> Am 11.11.2013 08:44, schrieb Alexey Kardashevskiy:
> > This converts +foo/-foo to "foo=on"/"foo=off" respectively when
> > QEMU parser is used for the command line options.
> >
> > "-cpu" parsers in x86 and other architectures should be
Hi all,
We've been seeing a problem lately running FreeBSD 9.1 and 9.2 (latest
stable) which causes the guest to crash during boot when QEMU is run on an
AMD processor with the 'xsave' flag set.
To reproduce this behaviour:
- Boot a FreeBSD 9.1 or 9.2 guest or even installation CD on an AMD
proc
Am 08.11.2013 um 04:26 hat Fam Zheng geschrieben:
> If backing file doesn't exist, the error message is confusing and
> misleading:
>
> $ qemu /tmp/a.qcow2
> qemu: could not open disk image /tmp/a.qcow2: Could not open file: No
> such file or directory
>
> But...
>
> $ ls /tmp/a.
Ping
http://patchwork.ozlabs.org/patch/280764/
On Sat, Oct 5, 2013 at 7:46 AM, Corey J. Boyle wrote:
> From: "Corey J. Boyle"
>
> Use target address rather than host address when performing
> non-GOT relocations
>
> Signed-off-by: Corey J. Boyle
> ---
> linux-user/flatload.c |2 +-
> 1
On Thu, 7 Nov 2013, Fabio Fantoni wrote:
> > The xenfb code is here:
> >
> > hw/display/xenfb.c
> >
> > It is registered here:
> >
> > hw/i386/xen_machine_pv.c:xen_init_pv
>
> Thanks, then I must search on qemu code what xenstore parameters enable xenfb
> and after search on xen, right?
Yes, o
provide a skeleton for a64 instruction decoding in translate-a64.c,
by dividing instructions into the classes defined by the
ARM Architecture Reference Manual(DDI0487A_a) C3
Signed-off-by: Claudio Fontana
---
The following patch has been started during Linaro Connect
by me and Alex Bennee.
The go
Il 11/11/2013 15:30, Owen Tuz ha scritto:
> Hi all,
>
> We've been seeing a problem lately running FreeBSD 9.1 and 9.2 (latest
> stable) which causes the guest to crash during boot when QEMU is run on
> an AMD processor with the 'xsave' flag set.
>
> To reproduce this behaviour:
>
> - Boot a Fr
Thanks, Paolo. We will test and let you know.
I'm not familiar with LWP (some reading to do there) - are there any plans
to support this in future, or is this just something that we're not
interested in emulating?
Best regards,
Owen
On Mon, Nov 11, 2013 at 3:25 PM, Paolo Bonzini wrote:
> Il 1
dmidecode itself should probably be checking at runtime what cpu
architecture it is running on so it can refuse to read /dev/mem on
systems which it doesn't know it understands.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://
From: Cole Robinson
The following commit introduced a migration incompatibility:
commit 568f0690fd9aa4d39d84b04c1a5dbb53a915c3fe
Author: David Gibson
Date: Thu Jun 6 18:48:49 2013 +1000
pci: Replace pci_find_domain() with more general pci_root_bus_path()
The issue is that i440fx savevm
From: Marcel Apfelbaum
This reverts commit a53ae8e934cd54686875b5bcfc2f434244ee55d6.
The patch being reverted introduced a low-priority memory region
covering all 64 bit pci address space. This exposed the following bugs
elsewhere in the code:
1. Some memory regions have INT64_MAX size, where
The following changes since commit c2d30667760e3d7b81290d801e567d4f758825ca:
rtc: remove dead SQW IRQ code (2013-11-05 20:04:03 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_anthony
for you to fetch changes up to ef9e455d645bed6d2
This reverts commit 818f86b88394b7b2b59d313e51043fe15a8004db.
This was a work-around for bugs elsewhere in the system,
exposed by commit a53ae8e934cd54686875b5bcfc2f434244ee55d6:
"hw/pci: partially handle pci master abort"
since that's reverted now, the work-around is not required for 1.7
anym
Am 06.11.2013 um 19:50 hat Max Reitz geschrieben:
> It should be possible to execute the QMP "drive-mirror" command in
> "none" sync mode and "absolute-paths" mode even for block devices
> lacking a backing file.
>
> "absolute-paths" does in fact not require a backing file to be present,
> as can
QEMU will currently crash if started with -no-acpi flag
since acpi build code probes the PM device which isn't present
in this configuration.
To fix, don't expose ACPI tables to guest when acpi has been
disabled from command line.
Fixes LP# 1248854
https://bugs.launchpad.net/qemu/+bug/1248854
Re
Am 07.11.2013 um 19:47 hat Max Reitz geschrieben:
> If the NewImageMode is "absolute-paths" but no backing file is available
> (e.g., when mirroring a device with an unbacked image), the target image
> will not be backed either. This patch updates the documentation in
> qapi-schema.json accordingly
From: Jason Wang
We delete without check whether it existed during exit. This will lead NULL
pointer deference since it was created conditionally depends on guest driver
status and features. So add a check of existence before trying to delete it.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Jason W
rom_add_blob never fails, and neither does rom_add_blob_fixed,
so there's no need to return value from it.
In fact, rom_add_blob_fixed was erroneously returning -1 unconditionally
which made the only system that checked the return value -M bamboo fail
to start.
Drop the return value and drop chec
Am 06.11.2013 um 16:06 hat Stefan Hajnoczi geschrieben:
> Signed-off-by: Stefan Hajnoczi
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 77edacf..6c63548 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -639,6 +639,8 @@ S: Suppo
13 bits left for pointer, which seems enough.
Signed-off-by: Michael S. Tsirkin
---
exec.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/exec.c b/exec.c
index 7e512db..39f76ee 100644
--- a/exec.c
+++ b/exec.c
@@ -84,9 +84,9 @@ typedef struct PhysPageEntry PhysPageEntr
From: Paolo Bonzini
As an alternative to commit 818f86b (exec: limit system memory
size, 2013-11-04) let's just make all address spaces 64-bit wide.
This eliminates problems with phys_page_find ignoring bits above
TARGET_PHYS_ADDR_SPACE_BITS and address_space_translate_internal
consequently messi
In preparation for dynamic page support, rename is_leaf
field to skip, telling us how many bits to skip to next level.
Set to 0 for leaf.
Signed-off-by: Michael S. Tsirkin
---
exec.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/exec.c b/exec.c
index d5ce3
From: Paolo Bonzini
The exec.c and translate-all.c radix trees are quite different, and
the exec.c one in particular is not limited to the CPU---it can be
used also by devices that do DMA, and in that case the address space
is not limited to TARGET_PHYS_ADDR_SPACE_BITS bits.
We want to make exec
At the moment, memory radix tree is already variable width, but it can
only skip the low bits of address.
This is efficient if we have huge memory regions but inefficient if we
are only using a tiny portion of the address space.
After we have built up the map, it's a simple matter to detect
confi
Am 06.11.2013 um 16:59 hat Charlie Shepherd geschrieben:
> v3:
> - Refix cow_update_bitmap and squash patches 1 & 3 together to ensuring
> that we only flush if
> necessary, patch 1 on its own would change this causing a regression.
> v2:
> - Fix bit position calculations in cow_update_bit
On Thu, Nov 07, 2013 at 06:29:40PM +0100, Paolo Bonzini wrote:
> Il 07/11/2013 17:47, Michael S. Tsirkin ha scritto:
> > That's on kvm with 52 bit address.
> > But where I would be concerned is systems with e.g. 36 bit address
> > space where we are doubling the cost of the lookup.
> > E.g. try i38
Quick - identify the bug in this code (from ui/curses.c):
static void curses_winch_handler(int signum)
{
struct winsize {
unsigned short ws_row;
unsigned short ws_col;
unsigned short ws_xpixel; /* unused */
unsigned short ws_ypixel; /* unused */
} ws;
Il 11/11/2013 17:40, Michael S. Tsirkin ha scritto:
> At the moment, exec ignores high bits in each address,
> for efficiency.
> This is incorrect: devices can do full 64 bit DMA, it's
> only the CPU that is limited by target address space.
> Using full 64 bit addresses was clocked at 12% performan
This change adds HOST_ABI_DIR (similar to TARGET_ABI_DIR) so the various
BSD OS dependent code can be seperated into its own directories rather
than using #ifdef's.
Signed-off-by: Stacey Son
---
Makefile.target |3 ++-
configure | 11 +++
2 files changed, 13 insertions(+), 1
Il 11/11/2013 16:43, Owen Tuz ha scritto:
> Thanks, Paolo. We will test and let you know.
> I'm not familiar with LWP (some reading to do there) - are there any
> plans to support this in future, or is this just something that we're
> not interested in emulating?
Given Linux does not support LWP,
On Mon, Nov 11, 2013 at 8:50 AM, Eric Blake wrote:
> Quick - identify the bug in this code (from ui/curses.c):
>
> static void curses_winch_handler(int signum)
> {
> struct winsize {
> unsigned short ws_row;
> unsigned short ws_col;
> unsigned short ws_xpixel; /* unus
This change adds support or stubs for file system (except stat) related system
calls including read(2), pread(2), readv(2), write(2), pwrite(2), writev(2),
pwritev(2), open(2), openat(2), close(2), closefrom(2), revoke(2), access(2),
eaccess(2), faccessat(2), chdir(2), fchdir(2), rename(2), rename
[v2]
- Rebases to 1.7.0-rc0. (Requires, however, Andreas Tobler's patch to
build: see
http://lists.nongnu.org/archive/html/qemu-devel/2013-11/msg0.html)
- Fixes deadlock in the _umtx_op() system call handler.
- Fixes race condition in mmap() system call handler.
- Makes qemu-mips (o32) usa
This change adds support or stubs for stat, directory, and file control related
system calls including stat(2), lstat(2), fstat(2), fstatat(2), nstat(),
nfstat(),
nlstat(), getfh(2), lgetfh(2), fhopen(2), fhstat(2), fhstatfs(2), statfs(2),
fstatfs(2), getfsstat(2), getdents(2), getdirentries(2), a
Update FreeBSD system call numbers in freebsd/syscall_nr.h.
Reviewed-by: Ed Maste
Signed-off-by: Stacey Son
---
bsd-user/freebsd/syscall_nr.h | 813 ++---
1 files changed, 445 insertions(+), 368 deletions(-)
diff --git a/bsd-user/freebsd/syscall_nr.h b/bsd-
This change adds support or stubs for socket related system calls including
accept(2), bind(2), connect(2), getpeername(2), getsockname(2), getsockopt(2),
setsockopt(2), listen(2), recvfrom(2), recvmsg(2), sendmsg(2), sendto(2),
socket(2), socketpair(2), shutdown(2), setfib(2), sctp_peeloff(2),
sct
Il 11/11/2013 17:56, Anthony Liguori ha scritto:
> On Mon, Nov 11, 2013 at 8:50 AM, Eric Blake wrote:
>> Quick - identify the bug in this code (from ui/curses.c):
>>
>> static void curses_winch_handler(int signum)
>> {
>> struct winsize {
>> unsigned short ws_row;
>> unsigned s
This change moves host OS and arch dependent code for the sysarch system
call related to the -strace functionality into the appropriate HOST_ABI_DIR
and TARGET_ABI_DIR directories.
Signed-off-by: Stacey Son
---
bsd-user/arm/syscall.h | 36 +++
bsd-user/arm/target_arch_sysar
This change add support for extended attribute and Access Control List
(ACL) related system calls including extattrctl(), extattr_set_file(2),
extattr_delete_file(2), extattr_set_fd(2), extattr_get_fd(2),
extattr_delete_fd(2), extattr_get_link(2), extattr_set_link(2),
extattr_delete_link(2), extatt
This change moves the system call handler for sysctl(2) and sysarch(2)
from syscall.c to the OS and arch dependent directories. This
eliminates many of the #ifdef's in syscall.c. These system call
handlers are now located in the host os and target arch directories.
Signed-off-by: Stacey Son
---
FreeBSD has it's own AES_set_decrypt_key, etc. in libcrypto. This
change fixes these conflicts and allows statically linking BSD
user mode qemu.
Signed-off-by: Stacey Son
---
include/qemu/aes.h |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/include/qemu/aes.h b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/11/2013 18:08, Eric Blake ha scritto:
>>> That said, aren't all signals in QEMU (except SIG_IPI) caught
>>> with signalfd and the handlers run synchronously in the
>>> iothread?
> signalfd is currently a Linux-only concept - what happens on BSD?
This change adds support or stubs for memory management related system calls
including mmap(2), munmap(2), mprotect(2), msync(2), mlock(2), munlock(2),
mlockall(2), munlockall(2), madvise(2), minherit(2), mincore(2), shm_open(2),
shm_unlink(2), shmget(2), shmctl(2), shmat(2), shmdt(2), vadvise(), s
On 11/11/2013 09:56 AM, Anthony Liguori wrote:
>> Here's a hint: ioctl() can clobber errno. But if a signal handler is
>> called in the middle of other code that is using errno, then the handler
>> MUST restore the value of errno before returning, if it is to guarantee
>> that the interrupted con
On 11 November 2013 17:05, Paolo Bonzini wrote:
> That said, aren't all signals in QEMU (except SIG_IPI) caught with
> signalfd and the handlers run synchronously in the iothread?
Eric specifically points out one which is not.
(I'm pretty sure that 'reinstall signal handler at
end of signal handl
I am working with two DMA engines at the moment. I want to be able to provide
guest access to a Crystal Beach DMA engine and a PLX 87xx DMA engine. Are
there any current efforts to provide support for these DMA engines? What I
have looked at so far indicates that they will need to have a QEMU
This change adds arm-bsd-user, mips-bsd-user, mips64-bsd-user,
mips64el-bsd-user, and mipsel-bsd-user as --target-list options to configure.
Signed-off-by: Stacey Son
---
default-configs/arm-bsd-user.mak |3 +++
default-configs/mips-bsd-user.mak |1 +
default-configs/mips64-bsd-
On 11 November 2013 16:56, Anthony Liguori wrote:
> On Mon, Nov 11, 2013 at 8:50 AM, Eric Blake wrote:
>> Here's a hint: ioctl() can clobber errno. But if a signal handler is
>> called in the middle of other code that is using errno, then the handler
>> MUST restore the value of errno before ret
Il 11/11/2013 17:43, Michael S. Tsirkin ha scritto:
> On Thu, Nov 07, 2013 at 06:29:40PM +0100, Paolo Bonzini wrote:
>> Il 07/11/2013 17:47, Michael S. Tsirkin ha scritto:
>>> That's on kvm with 52 bit address.
>>> But where I would be concerned is systems with e.g. 36 bit address
>>> space where w
On 11/11/2013 10:13 AM, Peter Maydell wrote:
> On 11 November 2013 17:05, Paolo Bonzini wrote:
>> That said, aren't all signals in QEMU (except SIG_IPI) caught with
>> signalfd and the handlers run synchronously in the iothread?
>
> Eric specifically points out one which is not.
> (I'm pretty sur
Il 11/11/2013 18:13, Peter Maydell ha scritto:
>> > That said, aren't all signals in QEMU (except SIG_IPI) caught with
>> > signalfd and the handlers run synchronously in the iothread?
> Eric specifically points out one which is not.
> (I'm pretty sure that 'reinstall signal handler at
> end of sig
At the moment, exec ignores high bits in each address,
for efficiency.
This is incorrect: devices can do full 64 bit DMA, it's
only the CPU that is limited by target address space.
Using full 64 bit addresses was clocked at 12% performance
hit on a microbenchmark.
To solve, teach pagetables to skip
On 11/11/2013 10:05 AM, Paolo Bonzini wrote:
>
> That said, aren't all signals in QEMU (except SIG_IPI) caught with
> signalfd and the handlers run synchronously in the iothread?
signalfd is currently a Linux-only concept - what happens on BSD?
--
Eric Blake eblake redhat com+1-919-301-3
On 11/11/2013 09:41 AM, Michael S. Tsirkin wrote:
> At the moment, memory radix tree is already variable width, but it can
> only skip the low bits of address.
>
> This is efficient if we have huge memory regions but inefficient if we
> are only using a tiny portion of the address space.
>
> Afte
On 11 Nov 2013, at 12:43, Stefan Hajnoczi wrote:
> Why is it necessary to push this task down into the host? I don't
> understand the advantage of this approach except that maybe it works
> around certain misconfigurations, I/O scheduler quirks, or plain old
> bugs - all of which should be inves
Il 11/11/2013 18:59, Alex Bligh ha scritto:
> > Why is it necessary to push this task down into the host? I don't
> > understand the advantage of this approach except that maybe it works
> > around certain misconfigurations, I/O scheduler quirks, or plain old
> > bugs - all of which should be inve
On Mon, Nov 11, 2013 at 8:50 PM, Eric Blake wrote:
> Quick - identify the bug in this code (from ui/curses.c):
>
> static void curses_winch_handler(int signum)
> {
> struct winsize {
> unsigned short ws_row;
> unsigned short ws_col;
> unsigned short ws_xpixel; /* unus
This function is used by a forthcomingQemu monitor command that dumps
contents of OpenFirmware Device Trees. It dumps contents of a buffer
as hex in the same format as the existing function but also also
appends any UTF-8 strings in human-readable format.
Like the existing hexdump function, this f
On 11 Nov 2013, at 18:01, Paolo Bonzini wrote:
> Il 11/11/2013 18:59, Alex Bligh ha scritto:
>>> Why is it necessary to push this task down into the host? I don't
>>> understand the advantage of this approach except that maybe it works
>>> around certain misconfigurations, I/O scheduler quirks,
Il 11/11/2013 19:32, Alex Bligh ha scritto:
>
> On 11 Nov 2013, at 18:01, Paolo Bonzini wrote:
>
>> Il 11/11/2013 18:59, Alex Bligh ha scritto:
Why is it necessary to push this task down into the host? I don't
understand the advantage of this approach except that maybe it works
ar
On 11/12/2013 01:13 AM, Claudio Fontana wrote:
> +/* C3.2 Branches, exception generating and system instructions */
> +static void disas_b_exc_sys(DisasContext *s, uint32_t insn)
> +{
> +switch (extract32(insn, 25, 7)) {
> +case 0x0a: case 0x4a: /* Unconditional branch (immediate) */
> +
Hi,
On 11/11/2013 09:47 AM, Gerd Hoffmann wrote:
On Fr, 2013-11-08 at 17:51 +0100, Jan Kiszka wrote:
On 2013-11-08 16:39, Gerd Hoffmann wrote:
Hi,
OK, then here is the first issue I ran into while trying libusbx (git
head, i.e. 1.0.17+: The new stack causes significant latency issues that
On 11/11/13 04:28, Phi Debian wrote:
> CU82$ /usr/bin/readelf -a vmcore
> Program Headers:
> Type Offset VirtAddrPhysAddr FileSizMemSiz Flg Align
> NOTE 0x74 0x 0x 0x000a0 0x000a0 0
> LOAD 0x000114 0x6000 0x6000 0x4000 0x40
Hi Laszlo,
On Mon, Nov 11, 2013 at 8:38 PM, Laszlo Ersek wrote:
>
> But first, I think you meant TARGET_PAGE_SIZE, not TARGET_PAGE_BITS, for
> the p_align field.
>
> So, the specs say for p_align:
>
>> As ``Program Loading'' describes in this chapter of the processor
>> supplement, loadable pro
On Mon, Nov 11, 2013 at 10:29 AM, Mike Day wrote:
> This function is used by a forthcomingQemu monitor command that dumps
> contents of OpenFirmware Device Trees. It dumps contents of a buffer
> as hex in the same format as the existing function but also also
> appends any UTF-8 strings in human-r
1 - 100 of 137 matches
Mail list logo
