On Sun, Apr 01, 2018 at 12:25:36AM +0530, Balamuruhan S wrote:
> expected_downtime value is not accurate with dirty_pages_rate * page_size,
> using ram_bytes_remaining would yeild it correct.
>
> Signed-off-by: Balamuruhan S
> ---
> migration/migration.c | 3 +--
> 1 file changed, 1 insertion(+)
On Thu, Mar 29, 2018 at 08:37:48AM +0200, Greg Kurz wrote:
> On Thu, 29 Mar 2018 16:25:37 +1100
> David Gibson wrote:
>
> > There are a couple places (one generic, one target specific) where we need
> > to get the host page size associated with a particular memory backend. I
> > have some upcomi
On Mon, Apr 02, 2018 at 11:22:06PM -0300, Eduardo Habkost wrote:
> On Thu, Mar 29, 2018 at 04:25:37PM +1100, David Gibson wrote:
> > There are a couple places (one generic, one target specific) where we need
> > to get the host page size associated with a particular memory backend. I
> > have some
Eric Auger reported the problem days ago that OOB broke ARM when running
with libvirt:
http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html
This patch fixes the problem.
It's not really needed now since we have turned OOB off now, but it's
still a bug fix, and it'll start to work w
In commit 223a23c198787328ae75bc65d84edf5fde33c0b6, we implemented a
workaround in the gluster driver to handle invalid values returned for
SEEK_DATA or SEEK_HOLE.
In some instances, these same invalid values can be seen in the posix
file handler as well - for example, it has been reported on FUSE
On 29/3/18 9:14 pm, Auger Eric wrote:
> Hi Alexey,
> On 29/03/18 03:55, Alexey Kardashevskiy wrote:
>> On 29/3/18 8:03 am, Auger Eric wrote:
>>> Hi Alexey, Alex,
>>> On 22/03/18 09:18, Alexey Kardashevskiy wrote:
The 567b5b309abe ("vfio/pci: Relax DMA map errors for MMIO regions") added
a
On Tue, 04/03 13:17, Lindsay Mathieson wrote:
> On 3 April 2018 at 13:11, Fam Zheng wrote:
>
> > On Tue, 04/03 12:59, Lindsay Mathieson wrote:
> > > Hi all, was looking at developing a block driver for qemu - have examined
> > > the drivers at:
> > >
> > > https://github.com/qemu/qemu/tree/mast
On 3 April 2018 at 13:11, Fam Zheng wrote:
> On Tue, 04/03 12:59, Lindsay Mathieson wrote:
> > Hi all, was looking at developing a block driver for qemu - have examined
> > the drivers at:
> >
> > https://github.com/qemu/qemu/tree/master/block
> >
> > And it seems straightforward enough.
> >
>
On Tue, 04/03 12:59, Lindsay Mathieson wrote:
> Hi all, was looking at developing a block driver for qemu - have examined
> the drivers at:
>
> https://github.com/qemu/qemu/tree/master/block
>
> And it seems straightforward enough.
>
> One thing that is unclear - all the drivers appear to be c
Hi all, was looking at developing a block driver for qemu - have examined
the drivers at:
https://github.com/qemu/qemu/tree/master/block
And it seems straightforward enough.
One thing that is unclear - all the drivers appear to be compiled directly
into qemu. Is there no way to load them dynam
On Sun, Apr 1, 2018 at 11:49 AM, Richard W.M. Jones
wrote:
> On Fri, Mar 30, 2018 at 10:08:23AM -0700, Michael Clark wrote:
> > Hi Peter,
> >
> > I had tested Richard's proper fix but we didn't have a PR or the required
> > Reviewed-by and Signed-off-by so I made the PR for the conservative fix,
On Mon, Apr 02, 2018 at 01:14:30PM +0800, Boqun Feng wrote:
> Ping ;-)
It missed soft feature freeze (March 13th), so I will queue this
for 2.13. Thanks!
>
> Regards,
> Boqun
>
> On Tue, Mar 20, 2018 at 08:08:15AM +0800, Boqun Feng wrote:
> > A new cpu model called "KnightsMill" is added to mo
On Thu, Mar 29, 2018 at 04:25:37PM +1100, David Gibson wrote:
> There are a couple places (one generic, one target specific) where we need
> to get the host page size associated with a particular memory backend. I
> have some upcoming code which will add another place which wants this. So,
> for
On Mon, 04/02 12:34, John Snow wrote:
>
>
> On 03/31/2018 03:08 AM, no-re...@patchew.org wrote:
> > 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
On Thu, Mar 29, 2018 at 11:10:21AM +0200, Greg Kurz wrote:
> The string returned by object_property_get_str() is dynamically allocated.
>
> Fixes: d8575c6c0242b
> Signed-off-by: Greg Kurz
Queued, thanks.
--
Eduardo
On Thu, Mar 29, 2018 at 11:09:46AM +0200, Greg Kurz wrote:
> The string returned by object_property_get_str() is dynamically allocated.
>
> Signed-off-by: Greg Kurz
Queued, thanks.
--
Eduardo
On Wed, Mar 28, 2018 at 08:48:54PM +, Justin Terry (VM) wrote:
> Hey Eduardo
>
> Responses inline. Thanks!
>
> > -Original Message-
> > From: Eduardo Habkost
> > Sent: Wednesday, March 28, 2018 10:51 AM
> > To: Justin Terry (VM)
> > Cc: qemu-devel@nongnu.org; pbonz...@redhat.com; r.
On 04/02/2018 02:05 PM, Laurent Vivier wrote:
> Le 02/04/2018 à 20:13, Rob Landley a écrit :
>>> The branch to use is q800-dev
...
>> It booted Linux to a shell prompt, I could wget a file from the internet, and
>> /home had the 2 gigabyte ext3 mount from the virtual block device.
>>
>> I.E. it wor
Change the code to avoid exiting QEMU if user provided DTB contains
manually specified /psci node and skip any /psci related fixups
instead.
Fixes: 4cbca7d9b4 ("hw/arm: Move virt's PSCI DT fixup code to
arm/boot.c")
Cc: Peter Maydell
Cc: Marc Zyngier
Cc: qemu-devel@nongnu.org
Cc: qemu-...@nongn
On 02.04.2018 21:34, John Snow wrote:
>
>
> On 04/02/2018 02:39 PM, Thomas Huth wrote:
>> On 29.03.2018 20:28, John Snow wrote:
>>>
>>>
>>> On 03/16/2018 01:39 AM, Thomas Huth wrote:
With one of my clean-up patches (see commit 1454509726719e0933c800), I
recently accidentially broke the
On 04/02/2018 02:39 PM, Thomas Huth wrote:
> On 29.03.2018 20:28, John Snow wrote:
>>
>>
>> On 03/16/2018 01:39 AM, Thomas Huth wrote:
>>> With one of my clean-up patches (see commit 1454509726719e0933c800), I
>>> recently accidentially broke the "-cdrom" parameter (more precisely
>>> "-drive if=
Le 02/04/2018 à 20:13, Rob Landley a écrit :
> On 03/30/2018 12:00 PM, Laurent Vivier wrote:
>> Le 30/03/2018 à 18:54, Rob Landley a écrit :
>>> On 03/20/2018 04:08 AM, Laurent Vivier wrote:> This series of patches is
>>> needed
>>> to fix a problem
in the m68k translator that can crash QEMU
On 29.03.2018 20:28, John Snow wrote:
>
>
> On 03/16/2018 01:39 AM, Thomas Huth wrote:
>> With one of my clean-up patches (see commit 1454509726719e0933c800), I
>> recently accidentially broke the "-cdrom" parameter (more precisely
>> "-drive if=scsi") on a couple of boards, since there was no er
On 03/26/2018 04:38 AM, David Hildenbrand wrote:
On 16.03.2018 00:24, Tony Krowiak wrote:
The VFIO AP device exploits interpretive execution of AP
instructions (APIE). APIE is enabled by setting a device attribute
via the KVM_SET_DEVICE_ATTR ioctl.
Signed-off-by: Tony Krowiak
---
target/s390
On 03/30/2018 12:00 PM, Laurent Vivier wrote:
> Le 30/03/2018 à 18:54, Rob Landley a écrit :
>> On 03/20/2018 04:08 AM, Laurent Vivier wrote:> This series of patches is
>> needed
>> to fix a problem
>>> in the m68k translator that can crash QEMU when translation
>>> cache has too many instructions
fadvise64_64 on xtensa passes advice as the second argument and so must
be handled similar to PPC.
This fixes glibc testsuite tests posix/tst-posix_fadvise and
posix/tst-posix_fadvise64.
Reviewed-by: Laurent Vivier
Signed-off-by: Max Filippov
---
linux-user/syscall.c | 2 +-
1 file changed, 1
mq_getsetattr implementation does not set errno correctly in case of
error. Also in the presence of both 2nd and 3rd arguments it calls both
mq_getattr and mq_setattr, whereas only the latter call would suffice.
Don't call mq_getattr in the presence of the 2nd argument. Don't copy
output back to u
This fixes glibc testsuite test rt/tst-clock2.
Signed-off-by: Max Filippov
---
linux-user/syscall.c | 12
1 file changed, 12 insertions(+)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 52e2f9c16479..924fd68efcdd 100644
--- a/linux-user/syscall.c
+++ b/linux-user/sy
In case of syscall restart request set pc back to the syscall
instruction.
Reviewed-by: Laurent Vivier
Signed-off-by: Max Filippov
---
linux-user/main.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/linux-user/main.c b/linux-user/main.c
index ba09b7d0c873..8907a8411411 100644
--- a/lin
- make target_ipc_perm fields match kernel definitions for xtensa;
- add target_semid64_ds with proper order of times and reserved fields
for little/big endian specific for xtensa;
- add missing reserved fields after time fields to the target_shmid_ds;
- fix types of shm_cpid, shm_lpid and shm_na
flush_window_regs uses wrong stack frame to save overflow registers in
call8 and call12 frames, which results in wrong register values in
callers of a function that received a signal.
Reimplement flush_window_regs closely following window overflow
sequence.
Signed-off-by: Max Filippov
---
linux-
in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20180402-xtensa
for you to fetch changes up to 64a563dd8dd6ca2661d96a2e4b69f0a5465cab94:
target/xtensa: linux-user: fix fadvise64 call (2018-04-02 04:15:35 -0700)
-
host_to_target_timespec may return error if target address could not be
locked, but it is ignored.
Propagate return value of host_to_target_timespec to the caller of
clock_gettime.
Reviewed-by: Laurent Vivier
Signed-off-by: Max Filippov
---
linux-user/syscall.c | 2 +-
1 file changed, 1 inserti
cpu_copy adds newly created CPU object to container/machine/unattached,
but does it w/o proper locking. As a result when multiple threads create
threads rapidly QEMU may abort with the following message:
GLib-CRITICAL **: g_hash_table_iter_next: assertion
'ri->version == ri->hash_table->versio
On 03/27/2018 08:02 AM, Cornelia Huck wrote:
On Fri, 16 Mar 2018 14:22:52 +0100
Halil Pasic wrote:
On 03/16/2018 11:42 AM, Pierre Morel wrote:
On 16/03/2018 00:24, Tony Krowiak wrote:
Introduces a VFIO based AP device. The device is defined via
the QEMU command line by specifying:
-de
On 03/16/2018 06:03 AM, Pierre Morel wrote:
On 16/03/2018 00:25, Tony Krowiak wrote:
This patch provides documentation describing the AP architecture and
design concepts behind the virtualization of AP devices. It also
includes an example of how to configure AP devices for exclusive
use of KVM g
On 03/26/2018 08:01 AM, Halil Pasic wrote:
On 03/26/2018 11:03 AM, Pierre Morel wrote:
+int ap_device_handle_pqap(S390CPU *cpu)
+{
+CPUS390XState *env = &cpu->env;
+int fc = 4 & (env->regs[0] >> 24);
+
+/*
+ * The Query Configuration Information (QCI) function (fc == 4) does not
On 03/26/2018 05:03 AM, Pierre Morel wrote:
On 26/03/2018 10:32, David Hildenbrand wrote:
On 16.03.2018 00:24, Tony Krowiak wrote:
If the CPU model indicates that AP facility is installed on
the guest (i.e., -cpu ,ap=on), then the expectation is that
the AP bus running in the guest will ini
On 03/31/2018 03:08 AM, no-re...@patchew.org wrote:
> 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: 2018032704564
On 03/26/2018 04:32 AM, David Hildenbrand wrote:
On 16.03.2018 00:24, Tony Krowiak wrote:
If the CPU model indicates that AP facility is installed on
the guest (i.e., -cpu ,ap=on), then the expectation is that
the AP bus running in the guest will initialize; however, if the
AP instructions a
Now that we have a mirror of this repo on git.qemu.org change the
submodule to use that and also update it to latest HEAD which has a
commit to fix a dangling symlink.
Signed-off-by: BALATON Zoltan
---
.gitmodules | 2 +-
roms/u-boot-sam460ex | 2 +-
2 files changed, 2 insertions(+), 2
On Mon, 2 Apr 2018, Michael Tokarev wrote:
roms/u-boot-sam460ex/tools/updater/stubs.c -
it is some strange symlink pointing to a strange place, probably should be
removed?
This does not seem to matter for building the rom image but this can be
fixed by converting it to a relative path. I've d
iotests 123 and 209 fail on 32-bit platforms. The culprit:
sizeof(extent) is wrong; we want sizeof(*extent). But since
the struct is 8 bytes, it happened to work on 64-bit platforms
where the pointer is also 8 bytes (nasty).
Fixes: 78a33ab58
Reported-by: Max Reitz
Signed-off-by: Eric Blake
Mes
It's never a good idea to blindly read for size bytes as
returned by the server without first validating that the size
is within bounds; a malicious or buggy server could cause us
to hang or get out of sync from reading further messages.
It may be smarter to try and teach the client to cope with
u
Having a more detailed log of the interaction between client and
server is invaluable in debugging how meta context negotiation
actually works.
Signed-off-by: Eric Blake
Message-Id: <20180330130950.1931229-1-ebl...@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
nbd/client.c | 2 +
The following changes since commit f184de7553272223d6af731d7d623a7cebf710b5:
Merge remote-tracking branch
'remotes/riscv/tags/riscv-qemu-2.12-critical-fixes' into staging (2018-03-31
09:42:33 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/ericb.git tags/pull-nbd-2018-
> On Apr 2, 2018, at 10:07 AM, qemu-devel-requ...@nongnu.org wrote:
>
> Message: 2
> Date: Mon, 2 Apr 2018 04:22:52 +0200
> From: Paolo Bonzini
> To: Rainer M?ller , qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] [qemu-web PATCH] download: Add instructions
> for MacPorts
> Message-ID: <
On 03/30/2018 11:32 AM, Vladimir Sementsov-Ogievskiy wrote:
> 30.03.2018 16:09, Eric Blake wrote:
>> Having a more detailed log of the interaction between client and
>> server is invaluable in debugging how meta context negotiation
>> actually works.
>>
>> Signed-off-by: Eric Blake
>> ---
>> nbd
On 03/30/2018 11:59 AM, Vladimir Sementsov-Ogievskiy wrote:
> 30.03.2018 02:18, Eric Blake wrote:
>> It's never a good idea to blindly read for size bytes as
>> returned by the server without first validating that the size
>> is within bounds; a malicious or buggy server could cause us
>> to hang o
On 03/29/2018 01:07 PM, Marc-André Lureau wrote:
Hi
On Thu, Mar 29, 2018 at 1:56 AM, Stefan Berger
wrote:
On 03/28/2018 11:41 AM, Marc-André Lureau wrote:
Hi
On Thu, Mar 1, 2018 at 8:59 PM, Stefan Berger
wrote:
+
+static const VMStateDescription vmstate_locty = {
+.name = "loc",
+.
I'm also seeing this issue with version 2.11. Currently Intel's oldest
available is 18.4 and this version reports an invalid checksum. The
E1000.dos file when loaded doesn't recognize the emulated NIC.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subs
Sparc as an extended sigaction structure containing
the field ka_restorer used in place of sa_restorer.
Define TARGET_ARCH_HAS_KA_RESTORER and use it
with sparc.
Signed-off-by: Laurent Vivier
---
linux-user/signal.c | 4 ++--
linux-user/syscall.c | 7 +--
linux-user/syscall_defs.
Signed-off-by: Laurent Vivier
---
linux-user/syscall_defs.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/linux-user/syscall_defs.h b/linux-user/syscall_defs.h
index 7473be518b..23f5bccf0e 100644
--- a/linux-user/syscall_defs.h
+++ b/linux-user/syscall_defs.h
@@ -2565,6 +2565,7 @@ struct ta
The sparc signal emulation is broken:
sparc has a special field called ka_restorer and to be used
in place of sa_restorer. Without it, the signal handler
exits and executes unexpected instructions.
(sparc64 has the same kind of problem but this change
doesn't fix it)
Once this problem is fixed, we
Le 02/04/2018 à 00:12, Max Filippov a écrit :
> fadvise64_64 on xtensa passes advice as the second argument and so must
> be handled similar to PPC.
>
> This fixes glibc testsuite tests posix/tst-posix_fadvise and
> posix/tst-posix_fadvise64.
>
> Signed-off-by: Max Filippov
> ---
> linux-user/s
On Mon, Apr 2, 2018 at 7:10 AM, Philippe Mathieu-Daudé wrote:
> [/var]/tmp full due to some jobs not cleaning well their workspaces?
Somehow our "make check" now keeps hanging in the container,
preventing it from being cleaned up correctly...
Will try to find time for it this week.
Fam
>
> On
On Mon, Apr 2, 2018 at 2:24 AM, Fam Zheng wrote:
> On Mon, 04/02 01:52, Jidong Xiao wrote:
>> Hi,
>>
>> A huge amount of documents has referenced this testing image:
>>
>> http://wiki.qemu.org/download/linux-0.2.img.bz2
>>
>> However, the image is no longer there. Is the image still available
>> s
Hi,
This series failed docker-quick@centos6 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: 20180329213857.15499-1-ehabk...@redhat.com
Subject: [Qemu-devel] [RFC 00/18] QEMU validat
On Mon, 04/02 01:52, Jidong Xiao wrote:
> Hi,
>
> A huge amount of documents has referenced this testing image:
>
> http://wiki.qemu.org/download/linux-0.2.img.bz2
>
> However, the image is no longer there. Is the image still available
> somewhere? Thanks.
According to the edit history of https
Hi,
A huge amount of documents has referenced this testing image:
http://wiki.qemu.org/download/linux-0.2.img.bz2
However, the image is no longer there. Is the image still available
somewhere? Thanks.
-Jidong
60 matches
Mail list logo
