Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1523675125-14022-1-git-send-email-...@godking.net
Subject: [Qemu-devel] [PATCH]
On 04/05/2018 04:13 PM, Emilio G. Cota wrote:
> tb_lock was needed when the function did retranslation. However,
> since fca8a500d519 ("tcg: Save insn data and use it in
> cpu_restore_state_from_tb") we don't do retranslation.
>
> Get rid of the comment.
>
> Signed-off-by: Emilio G. Cota
On 04/05/2018 04:13 PM, Emilio G. Cota wrote:
> Use the recently-gained QHT feature of returning the matching TB if it
> already exists. This allows us to get rid of the lookup we perform
> right after acquiring tb_lock.
>
> Suggested-by: Richard Henderson
> Signed-off-by:
On 04/05/2018 04:13 PM, Emilio G. Cota wrote:
> +static __thread bool page_collection_locked;
> +
> +void assert_page_collection_locked(bool val)
> +{
> +tcg_debug_assert(page_collection_locked == val);
> +}
> +
> +static inline void set_page_collection_locked(bool val)
> +{
> +
On 04/05/2018 04:13 PM, Emilio G. Cota wrote:
> +#ifdef CONFIG_DEBUG_TCG
> +
> +struct page_lock_debug {
> +const PageDesc *pd;
> +QLIST_ENTRY(page_lock_debug) entry;
> +};
> +
> +static __thread QLIST_HEAD(, page_lock_debug) page_lock_debug_head;
> +
> +static struct page_lock_debug
On 04/05/2018 04:13 PM, Emilio G. Cota wrote:
> +/**
> + * struct page_collection - tracks a set of pages (i.e. page_entry's)
> + * @tree: Binary search tree (BST) of the pages, with key == page index
> + * @max:Pointer to the page in @tree with the highest page index
> + *
> + * To avoid
Implement a QMP command similar to the HMP's "info usbhost" command.
This allows a QMP client to query which USB devices may be available
for redirection. Because the availability of the command needs to
depend on the target's (not the build host's) USB configuration,
a qmp_nousb.c is provided for
Code inspection shows that qcow2_update_cluster_refcount() no longer
calls bdrv_flush(). This issue has been fixed.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Can you still reproduce the issue with a recent Linux kernel and the
latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
zIPL boot menu entries can be non-sequential. Let's account
for this issue for the s390 enumerated boot menu. Since we
can no longer print a range of available entries to the
user, we have to present a list of each available entry.
An example of this menu:
s390-ccw Enumerated Boot Menu.
On 04/13/2018 01:45 PM, Marc-André Lureau wrote:
> Signed-off-by: Marc-André Lureau
Reviewed-by: Philippe Mathieu-Daudé
> ---
> hw/acpi/aml-build.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/acpi/aml-build.c
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
zIPL boot menu entries can be non-sequential. Let's account
for this issue for the s390 zIPL boot menu. Since this boot
menu is actually an imitation and is not completely capable
of everything the real zIPL menu can do, let's also print a
different banner to the user.
Signed-off-by: Collin
Change Log:
v2
- added r-b's
- s/zipl_println/zipl_print_entry
- prints entry and returns entry number
- while loop now handles valid_entries
These patches fix the following:
- The QEMU zIPL boot menu does not allow accurate selection of
Rename the loadparm char array in main.c to loadparm_str and
increased the size by one byte to account for a null termination
when converting the loadparm string to an int via atoui. We
also allow the boot menu to be enabled when loadparm is set to
an empty string or a series of spaces.
The MAX_TABLE_ENTRIES constant has a name that is too generic. As we
want to declare a limit for boot menu entries, let's rename it to a more
fitting MAX_BOOT_ENTRIES and set its value to 31 (30 boot entries and
1 default entry). Also we move it from bootmap.h to s390-ccw.h to make
it available
Looks like this has been fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c170aad8b057223b1139d7
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
This error message comes from libvirt, not from QEMU, so please report
the error there if it still persists: https://libvirt.org/bugs.html
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Closing this ticket now, since it's not about upstream QEMU code.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1362635
Title:
bdrv_read
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1190525
Title:
fdisk still shows the "/dev/sdb" partitions even after the removal of
scsi disk
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
On Fri, Apr 13, 2018 at 10:26:03PM +0300, Nir Soffer wrote:
> When a management application expose images using qemu-nbd, it needs a
> secure way to allow temporary access to the disk. Using a random export
> name can solve this problem:
>
>
On 04/13/2018 01:44 PM, Vladimir Sementsov-Ogievskiy wrote:
>
> will add, as always, thank you for natural rewording) Hm, I have a
> question: why do you often use double white-space " " between
> sentences? Is it something meaningful?
There is some GREAT DEBATE in the English-speaking world
FYI: To workaround this issue you can limit the docker container to a
single cpu like this:
docker run --cpuset-cpus 0 -it cross-test3 go build hello.go
This works for docker build as well.
docker build--cpuset-cpus 0 .
--
You received this bug notification because you are a member of
Add new test module for tesing the --nolist option.
Signed-off-by: Nir Soffer
---
tests/qemu-iotests/214 | 46 ++
tests/qemu-iotests/214.out | 2 ++
tests/qemu-iotests/group | 1 +
3 files changed, 49 insertions(+)
create
When a management application expose images using qemu-nbd, it needs a
secure way to allow temporary access to the disk. Using a random export
name can solve this problem:
nbd://server:10809/22965f19-9ab5-4d18-94e1-cbeb321fa433
Assuming that the url is passed to the user in a secure way, and
Add few helpers for running external commands:
- CommandFailed: exception, keeping all the info related to a failed
command, and providing a useful error message. (Unfortunately
subprocess.CalledProcessError does not).
- run(): run a command collecting output from the underlying process
oVirt uses random URLs to expose images temporarily via HTTPS. We would
like to integrated qemu-nbd in the same system, proving a user an easy
and uniform way to access an image - either using HTTPS:
https://server:54322/images/dc72d3cc-b933-45e8-89a2-e028e1c2ef3d
Or using NBD over TLS:
I missed a step for reproduction. Step 1 should be:
docker run --rm --privileged multiarch/qemu-user-static:register
This modprobes binfmt and registers qemu-ppc64le-static as the interpreter for
ppc64le executables.
--
You received this bug notification because you are a member of qemu-
On 04/13/2018 04:23 AM, Peter Maydell wrote:
> The MIPS TCG target makes the assumption that the offset from the
> target env pointer to the tlb_table is less than about 64K. This
> used to be true, but gradual addition of features to the Arm
> target means that it's no longer true there. This
On 04/12/2018 04:02 AM, Peter Maydell wrote:
> AArch64 stack frames include a 'frame record' which holds a pointer
> to the next frame record in the chain and the LR on entry to the
> function. The procedure calling standard doesn't mandate where
> exactly this frame record is in the stack frame,
> Cc: Michael Clark
> Cc: Palmer Dabbelt
> Cc: Sagar Karandikar
> Cc: Bastian Koppelmann
>
> Signed-off-by: Emilio G. Cota
> ---
> target/riscv/translate.c | 72
>
On 04/11/2018 08:45 AM, Laurent Vivier wrote:
> Instead of calling setup_frame() conditionally to a list of known targets,
> define TARGET_ARCH_HAS_SETUP_FRAME if the target provides the function
> and call it only if the macro is defined.
>
> Move declarations of setup_frame() and
On Apr 12 17:41, Peter Maydell wrote:
> On 16 March 2018 at 20:31, Aaron Lindsay wrote:
> > It was shifted to the left one bit too few.
> >
> > Signed-off-by: Aaron Lindsay
> > ---
> > target/arm/helper.c | 2 +-
> > 1 file changed, 1
On 04/06/2018 08:19 AM, Emilio G. Cota wrote:
> Notes:
>
> - Did not convert {num,max}_insns, since the corresponding code
> will go away in the next patch.
>
> - ctx->pc becomes ctx->base.pc_next, and ctx->next_pc becomes ctx->pc_tmp.
>
> While at it, convert the remaining tb->cflags readers
On 04/06/2018 08:20 AM, Emilio G. Cota wrote:
> Cc: Michael Clark
> Cc: Palmer Dabbelt
> Cc: Sagar Karandikar
> Cc: Bastian Koppelmann
> Signed-off-by: Emilio G. Cota
> ---
>
Handle new NBD meta namespace: "qemu", and corresponding queries:
"qemu:dirty-bitmap:".
With new metadata context negotiated, BLOCK_STATUS query will reply
with dirty-bitmap data, converted to extents. New public function
nbd_export_bitmap selects bitmap to export. For now, only one bitmap
may be
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
qapi/block.json | 23 +++
blockdev-nbd.c | 23 +++
2 files changed, 46 insertions(+)
diff --git a/qapi/block.json b/qapi/block.json
index c694524002..cc0e607b5b 100644
---
The helper will be reused for bitmaps namespace.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Eric Blake
---
nbd/server.c | 40 +++-
1 file changed, 27 insertions(+), 13 deletions(-)
diff --git
Hi all.
This is a proposal and realization of new NBD meta context:
qemu. (I hope to send corresponding proposal to NBD protocol soon)
New possible queries will look like:
qemu:dirty-bitmap:
Mapping from export-bitmap-name to BdrvDirtyBitmap is done through qmp
command nbd-server-add-bitmap.
On 04/13/2018 02:06 PM, Philippe Mathieu-Daudé wrote:
> On 04/13/2018 01:59 PM, Halil Pasic wrote:
On 04/13/2018 04:30 PM, Thomas Huth wrote:
> "size_t" should be an unsigned type - the signed counterpart is called
> "ssize_t" in the C standard instead. Thus we should also use this
On 04/13/2018 01:59 PM, Halil Pasic wrote:
>>> On 04/13/2018 04:30 PM, Thomas Huth wrote:
"size_t" should be an unsigned type - the signed counterpart is called
"ssize_t" in the C standard instead. Thus we should also use this
>>> The first sentence sounds like ssize_t is too a type
Hi Igor,
On 12/04/18 18:40, Igor Mammedov wrote:
> platform-bus were using machine_done notifier to get and map
> (assign irq/mmio resources) dynamically added sysbus devices
> after all '-device' options had been processed.
> That however creates non obvious dependencies on ordering of
>
21.03.2018 18:05, Eric Blake wrote:
On 03/21/2018 07:19 AM, Vladimir Sementsov-Ogievskiy wrote:
The helper will be reused for bitmaps namespace.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
nbd/server.c | 41 -
1 file
On 2018-02-28 15:20, Alberto Garcia wrote:
> On Wed 28 Feb 2018 03:01:33 PM CET, Eric Blake wrote:
>
The refcount table has implications on the maximum host file size; a
larger cluster size is required for the refcount table to cover
larger offsets.
>>>
>>> Why is this? Because of
On 04/13/2018 05:50 PM, Thomas Huth wrote:
> On 13.04.2018 17:28, Halil Pasic wrote:
>>
>> On 04/13/2018 04:30 PM, Thomas Huth wrote:
>>> "size_t" should be an unsigned type - the signed counterpart is called
>>> "ssize_t" in the C standard instead. Thus we should also use this
>> The first
Signed-off-by: Marc-André Lureau
---
hw/acpi/aml-build.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
index 3fa557cea1..1e43cd736d 100644
--- a/hw/acpi/aml-build.c
+++ b/hw/acpi/aml-build.c
@@ -627,7
Hi Kirti, what do you think of the pre-copy interface in this series?
Thanks,
Yulei
> -Original Message-
> From: Zhang, Yulei
> Sent: Tuesday, April 10, 2018 2:02 PM
> To: qemu-devel@nongnu.org
> Cc: Tian, Kevin ; joonas.lahti...@linux.intel.com;
>
Hi,
This series aims to get rid of the distinction between QObject, that
must use qobject_incref/qobject_decref and its various derived types
that have to use QINCREF/QDECREF. Instead, replace it with
qobject_ref/qobject_unref for all types.
v4:
- rename QObjectCommon->QObjectBase_
- add back
By moving the base fields to a QObjectBase_, QObject can be a type
which also has a 'base' field. This allows to write a generic
QOBJECT() macro that will work with any QObject type, including
QObject itself. The container_of() macro ensures that the object to
cast has a QObjectBase_ base field,
Following a discussion on the mailing list: while it may be convenient
to accept NULL value in qobject_unref() (for similar reasons as free()
accepts NULL), it is a probably a bad idea to accept NULL argument in
qobject_ref().
Furthermore, it is convenient and more clear to call qobject_ref() at
All QObject types have the base QObject as first field. This allows to
simplify qobject_to() and will allow further simplification in
following patch.
Signed-off-by: Marc-André Lureau
---
include/qapi/qmp/qobject.h | 5 ++---
qobject/qobject.c | 9 +
On 04/13/2018 05:29 PM, Peter Maydell wrote:
> On 13 April 2018 at 16:24, Bastian Koppelmann
> wrote:
>> However, my risu-like tests found another flag raising problem with
>> float32_div. I'll investigate it on Monday.
>
> Is it a regression from our previous
On 29/03/2018 18:23, Eric Blake wrote:
>>
>> +/**
>> + * qobject_ref(): Increment QObject's reference count
>> + */
>> +#define qobject_ref(obj) \
>> + qobject_ref(QOBJECT(obj))
>
> ...below the functions of the same name. C preprocessor rules guarantee
> that you
Hi
On Thu, Mar 29, 2018 at 6:10 PM, Eric Blake wrote:
> On 03/29/2018 10:48 AM, Marc-André Lureau wrote:
>>
>> Following a discussion on the mailing list: while it may be convenient
>> to accept NULL value in qobject_unref() (for similar reasons as free()
>> accepts NULL), it
** Summary changed:
- qemu/pc-bios/s390-ccw/libc.c:82: bad test ?
+ pc-bios/s390-ccw/libc: size_t should be unsigned
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1753437
Title:
Ian Jackson writes:
> This allows the caller to specify a uid and gid to use, even if there
> is no corresponding password entry. This will be useful in certain
> Xen configurations.
>
> We don't support just -runas because: (i) deprivileging without
> calling
On 13.04.2018 17:28, Halil Pasic wrote:
>
>
> On 04/13/2018 04:30 PM, Thomas Huth wrote:
>> "size_t" should be an unsigned type - the signed counterpart is called
>> "ssize_t" in the C standard instead. Thus we should also use this
>
> The first sentence sounds like ssize_t is too a type
On 13 April 2018 at 16:28, Halil Pasic wrote:
>
>
> On 04/13/2018 04:30 PM, Thomas Huth wrote:
>> "size_t" should be an unsigned type - the signed counterpart is called
>> "ssize_t" in the C standard instead. Thus we should also use this
>
> The first sentence sounds
On Wed, Apr 11, 2018 at 08:59:32AM +0300, Oleksandr Andrushchenko wrote:
> On 04/10/2018 08:26 PM, Dongwon Kim wrote:
> > On Tue, Apr 10, 2018 at 09:37:53AM +0300, Oleksandr Andrushchenko wrote:
> > > On 04/06/2018 09:57 PM, Dongwon Kim wrote:
> > > > On Fri, Apr 06, 2018 at 03:36:03PM +0300,
On 13 April 2018 at 16:24, Bastian Koppelmann
wrote:
> However, my risu-like tests found another flag raising problem with
> float32_div. I'll investigate it on Monday.
Is it a regression from our previous (2.11) behaviour?
thanks
-- PMM
On 04/13/2018 04:30 PM, Thomas Huth wrote:
> "size_t" should be an unsigned type - the signed counterpart is called
> "ssize_t" in the C standard instead. Thus we should also use this
The first sentence sounds like ssize_t is too a type defined by some
C standard. Is it or does ssize_t come
On 04/13/2018 04:07 PM, Peter Maydell wrote:
> On 13 April 2018 at 15:06, Bastian Koppelmann
> wrote:
>> On 04/13/2018 04:03 PM, Alex Bennée wrote:
>>> The re-factor broke the raising of INVALID when NaN/Inf is passed to
>>> the float_to_int conversion functions.
On 6 April 2018 at 16:17, Christophe Lyon wrote:
> Hello,
>
> This patch series implements the QEMU contribution of the FDPIC
> ABI for ARM targets.
> I am currently working on updating the patches for the other toolchain
> components, and will upstream them soon. This
On 6 April 2018 at 16:17, Christophe Lyon wrote:
> The FDPIC restorer needs to deal with a function descriptor, hence we
> have to extend 'retcode' such that it can hold the instructions needed
> to perform this.
>
> The restorer sequence uses the same thumbness as the
On Fri, Apr 13, 2018 at 03:23:36PM +0100, Peter Maydell wrote:
> The MIPS TCG target makes the assumption that the offset from the
> target env pointer to the tlb_table is less than about 64K. This
> used to be true, but gradual addition of features to the Arm
> target means that it's no longer
On 6 April 2018 at 16:17, Christophe Lyon wrote:
> Add FDPIC info into image_info structure since interpreter info is on
> stack and needs to be saved to be accessed later on.
>
> Co-Authored-By: Mickaël Guêné
> Signed-off-by: Christophe Lyon
On 6 April 2018 at 16:17, Christophe Lyon wrote:
> Adds --enable-fdpic and --disable-fdpic configure options. This
> feature is disabled by default, that's why it is not described in the
> "Optional features" help section (which are enabled by default if
> possible).
>
>
On 6 April 2018 at 16:17, Christophe Lyon wrote:
> Co-Authored-By: Mickaël Guêné
> Signed-off-by: Christophe Lyon
>
> diff --git a/linux-user/arm/target_syscall.h b/linux-user/arm/target_syscall.h
> index 94e2a42..afc0772
On Fri 13 Apr 2018 04:45:15 PM CEST, Max Reitz wrote:
> OK, now that that's out of the way... I'm wondering why you want to
> add this to the qemu tree? If you'd written an iotest that would make
> use of it, sure. But if it's just for debugging, then I'd personally
> think it would be better
On 2018-03-14 09:29, Alberto Garcia wrote:
> The L2 and refcount caches have default sizes that can be overridden
> using the l2-cache-size and refcount-cache-size (an additional
> parameter named cache-size sets the combined size of both caches).
>
> Unless forced by one of the aforementioned
On 04/13/2018 02:14 AM, Thomas Huth wrote:
> On 10.04.2018 17:01, Collin Walling wrote:
>> zIPL boot menu entries can be non-sequential. Let's account
>> for this issue for the s390 zIPL boot menu. Since this boot
>> menu is actually an imitation and is not completely capable
>> of everything the
On 04/13/2018 10:30 AM, Thomas Huth wrote:
> "size_t" should be an unsigned type - the signed counterpart is called
> "ssize_t" in the C standard instead. Thus we should also use this
> convention in the s390-ccw firmware to avoid confusion. I checked the
> sources, and apart from one spot in
On 2018-03-28 15:38, Alberto Garcia wrote:
> This script takes a qcow2 image and dumps its metadata: header,
> snapshot table and some extensions (although not all qcow2 features
> are supported yet).
>
> It can also display a list of all host clusters and the guest -> host
> address mappings, so
Looking through old bug tickets... have this issue been fixed, i.e.
could we close this ticket nowadays? Or is there still something left to
do?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
13.04.2018 17:31, Vladimir Sementsov-Ogievskiy wrote:
Handle nbd CACHE command. Just do read, without sending read data back.
Cache mechanism should be done by exported node driver chain.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/nbd.h | 3 ++-
On 04/13/2018 11:30 AM, Thomas Huth wrote:
> "size_t" should be an unsigned type - the signed counterpart is called
> "ssize_t" in the C standard instead. Thus we should also use this
> convention in the s390-ccw firmware to avoid confusion. I checked the
> sources, and apart from one spot in
On 2018-04-10 18:05, Alberto Garcia wrote:
> Hi,
>
> while reviewing one previous patch about data corruption and
> compressed clusters we discussed that the documentation doesn't
> clarify that L2 entries for compressed clusters are not supposed to
> have the OFLAG_COPIED bit set.
>
> Here's a
On 13/04/2018 16:33, Roman Kagan wrote:
> As of mainline linux commit 5a485803221777013944cbd1a7cd5c62efba3ffa
> "x86/hyper-v: move hyperv.h out of uapi" by Vitaly Kuznetsov, no linux
> uapi header includes it, so we no longer need to create a stub for it.
>
> Cc: Vitaly Kuznetsov
As of mainline linux commit 5a485803221777013944cbd1a7cd5c62efba3ffa
"x86/hyper-v: move hyperv.h out of uapi" by Vitaly Kuznetsov, no linux
uapi header includes it, so we no longer need to create a stub for it.
Cc: Vitaly Kuznetsov
Signed-off-by: Roman Kagan
Handle nbd CACHE command. Just do read, without sending read data back.
Cache mechanism should be done by exported node driver chain.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/nbd.h | 3 ++-
nbd/server.c| 10 ++
2 files changed, 8
"size_t" should be an unsigned type - the signed counterpart is called
"ssize_t" in the C standard instead. Thus we should also use this
convention in the s390-ccw firmware to avoid confusion. I checked the
sources, and apart from one spot in libc.c (which now uses ssize_t with
this patch), the
The MIPS TCG target makes the assumption that the offset from the
target env pointer to the tlb_table is less than about 64K. This
used to be true, but gradual addition of features to the Arm
target means that it's no longer true there. This results in
the build-time assertion failing:
In file
On 2018-04-12 19:07, Alberto Garcia wrote:
> Hello,
>
> I mentioned this some time ago, but I'd like to retake it now: I'm
> checking how to copy arbitrary nodes on a backing chain, so if I have
> e.g.
>
>[A] <- [B] <- [C] <- [D]
>
> I'd like to end up with
>
>[A] <- [E] <- [C] <- [D]
On 04/12/2018 03:41 PM, Alex Bennée wrote:
> Bastian Koppelmann writes:
>
>> On 04/11/2018 01:01 PM, Alex Bennée wrote:
>>> Bastian Koppelmann writes:
>>>
On 04/10/2018 10:07 PM, Alex Bennée wrote:
> Yeah it looks like it
On 13 April 2018 at 15:18, Laurent Vivier wrote:
> Le 12/04/2018 à 16:02, Peter Maydell a écrit :
>> @@ -1850,12 +1856,6 @@ static void target_setup_frame(int usig, struct
>> target_sigaction *ka,
>> fr_ofs = layout.total_size;
>> layout.total_size += sizeof(struct
Le 12/04/2018 à 16:02, Peter Maydell a écrit :
> AArch64 stack frames include a 'frame record' which holds a pointer
> to the next frame record in the chain and the LR on entry to the
> function. The procedure calling standard doesn't mandate where
> exactly this frame record is in the stack
On 13 April 2018 at 15:03, Alex Bennée wrote:
> The re-factor broke the raising of INVALID when NaN/Inf is passed to
> the float_to_int conversion functions. round_to_uint_and_pack got this
> right for NaN but also missed out the Inf handling.
>
> Fixes
Alexey Kardashevskiy writes:
> There is already 'device-list-properties' which does most of the job,
> however it does not handle everything returned by qom-list-types such
> as machines as they inherit directly from TYPE_OBJECT and not TYPE_DEVICE.
> It does not handle abstract
On 04/13/2018 04:03 PM, Alex Bennée wrote:
> The re-factor broke the raising of INVALID when NaN/Inf is passed to
> the float_to_int conversion functions. round_to_uint_and_pack got this
> right for NaN but also missed out the Inf handling.
>
> Fixes https://bugs.launchpad.net/qemu/+bug/1759264
>
Hi Peter,
On 13/04/18 16:06, Peter Maydell wrote:
> On 13 April 2018 at 15:01, Auger Eric wrote:
>> On 13/04/18 15:41, Peter Maydell wrote:
>>> I think it would be better to explicitly check "do we have
>>> support for split redistributors" rather than looking at
>>>
v2: Rebase on top of master
v3: Fix the json format (Eric Blake)
Fix a comparison issue (Gerd Hoffmann)
Signed-off-by: Elie Tournier
---
qapi/ui.json | 20 +++-
vl.c | 10 +-
2 files changed, 24 insertions(+), 6 deletions(-)
diff
Daniel Henrique Barboza writes:
> Ping
Michael, you reviewed v4 (at least in part), can you have a look?
On 13 April 2018 at 15:06, Bastian Koppelmann
wrote:
> On 04/13/2018 04:03 PM, Alex Bennée wrote:
>> The re-factor broke the raising of INVALID when NaN/Inf is passed to
>> the float_to_int conversion functions. round_to_uint_and_pack got this
>> right for NaN but
Hi,
v2: Rebase on top of master
v3: Fix the json format (Eric Blake)
Move DisplayOptions from ui/sdl2.c to include/ui/sdl2.h (Gerd Hoffmann)
Fix a comparison issue (Gerd Hoffmann)
Currently, virglrenderer [1] support OpenGL ES 2.0 on the guest side
and OpenGL ES 3.0 on the host side.
Signed-off-by: Elie Tournier
---
qemu-options.hx | 2 +-
ui/sdl2-gl.c| 19 +--
vl.c| 4
3 files changed, 22 insertions(+), 3 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index ca4e412f2f..333dd1f1c8 100644
---
On 13 April 2018 at 15:01, Auger Eric wrote:
> On 13/04/18 15:41, Peter Maydell wrote:
>> I think it would be better to explicitly check "do we have
>> support for split redistributors" rather than looking at
>> KVM_MAX_VCPUS. It's not impossible that a distro kernel
>>
Hi,
The float_invalid patch now handles the Inf case as well and includes
the fix to round_to_uint_and_pack.
Alex Bennée (1):
fpu/softfloat: raise float_invalid for NaN/Inf in
round_to_int_and_pack
Emilio G. Cota (1):
softfloat: fix {min,max}nummag for same-abs-value inputs
Suggested-by: Gerd Hoffmann
Signed-off-by: Elie Tournier
---
include/ui/sdl2.h | 1 +
ui/sdl2.c | 10 +-
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/include/ui/sdl2.h b/include/ui/sdl2.h
index
1 - 100 of 170 matches
Mail list logo