On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
>
> ---
>
> Updated copyright info
> Also split virtio-pci.h bits
> ---
> hw/virtio/Makefile.objs | 3 ++
> hw/virtio/vhost-vsock-pci.c | 82 +
> hw/v
On Thu 13 Dec 2018 06:51:54 PM CET, Markus Armbruster wrote:
> Patch created mechanically by rerunning:
>
> $ spatch --sp-file scripts/coccinelle/qobject.cocci \
> --macro-file scripts/cocci-macro-file.h \
> --dir block --in-place
>
> Signed-off-by: Markus Armbruster
Review
On 2018/12/7 上午12:59, Vincenzo Maffione wrote:
Improvements to the netmap backend, mostly to fix the handling of
incomplete multi-slot packets.
This has been tested with and without jumbo frames, using pkt-gen
to send 60, 1500, 5000 or 9000 bytes packets between two VMs connected
through a VALE
On 2018-12-13 22:00, Juan Quintela wrote:
> For consistency with other devices, rename
> virtio_host_{initfn,pci_info} to virtio_input_host_{initfn,info}.
>
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
> ---
> default-configs/virtio.mak| 1 +
> hw/virtio/Makefile.objs
From: Marc-André Lureau
Wrap generated enum and struct members and their supporting code with
#if/#endif, using the .ifcond members added in the previous patches.
We do enum and struct in a single patch because union tag enum and the
associated variants tie them together, and dealing with that t
configure gets the version number from VERSION, and writes it to
config-host.mak. The make dependency for that is missing. Because of
that, a rebuild after a VERSION change may not pick up the change.
Fix that.
Signed-off-by: Markus Armbruster
---
Makefile | 2 +-
1 file changed, 1 insertion(+
git-request-pull master public pull-qapi-2018-12-13-v2
The following changes since commit c3ec0fa1a8e815ecfec9eabb9c20ee206c313e07:
Merge remote-tracking branch 'remotes/armbru/tags/pull-monitor-2018-12-12'
into staging (2018-12-13 13:41:44 +)
are available in the Git repository at:
git
On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
> ---
> hw/virtio/Makefile.objs | 1 +
> hw/virtio/virtio-input-pci.c | 154 +++
> hw/virtio/virtio-pci.c | 113 -
> hw/virt
Resent by accident, please ignore this copy, and use the original instead.
configure gets the version number from VERSION, and writes it to
config-host.mak. The make dependency for that is missing. Because of
that, a rebuild after a VERSION change may not pick up the change.
Fix that.
Signed-off-by: Markus Armbruster
---
Makefile | 2 +-
1 file changed, 1 insertion(+
On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
Reviewed-by: Thomas Huth
14.12.2018 2:28, Paolo Bonzini wrote:
> On 11/12/18 17:43, Vladimir Sementsov-Ogievskiy wrote:
>> +ThreadPool *pool = aio_get_thread_pool(bdrv_get_aio_context(bs));
>> +
>> +while (s->nb_threads >= QCOW2_MAX_THREADS) {
>> +qemu_co_queue_wait(&s->thread_task_queue, NULL);
>> +}
>
On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
>
> ---
>
> Also disable virtio9p test (lvivier)
[...]
> diff --git a/tests/Makefile.include b/tests/Makefile.include
> index dd7c882cc5..90d33bb058 100644
> --- a/tests/Makefile.include
> +++
On 2018-12-13 22:00, Juan Quintela wrote:
> Signed-off-by: Juan Quintela
> ---
> default-configs/virtio.mak | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/default-configs/virtio.mak b/default-configs/virtio.mak
> index 5ae4a61018..ecb4420e74 100644
> --- a/default-confi
On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
> ---
> hw/virtio/Makefile.objs | 1 +
> hw/virtio/vhost-user-scsi-pci.c | 101
> hw/virtio/virtio-pci.c | 58 --
> hw/virti
Li Qiang 于2018年12月14日周五 上午9:46写道：
> Hi all,
>
> Here is the error.
>
> GTESTER check-qtest-x86_64
> Unable to get file status flag on fd 21860: Bad file descriptor(errno=9)
> GTESTER check-qtest-aarch64
> Broken pipe
> GTester: last random seed: R02S3f0d6981dd97231d06e0b2966baf94b9
> Unable t
On 13/12/2018 17:26, Tony Krowiak wrote:
If the maximum number of devices allowed on a bus is 1 and a device
which is plugged into the bus is subsequently unplugged, attempting to replug
the device fails with error "Bus 'xxx' does not support hotplugging".
The "error" is detected in the qbus_is_f
On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
> ---
> hw/virtio/Makefile.objs| 1 +
> hw/virtio/vhost-scsi-pci.c | 95 ++
> hw/virtio/virtio-pci.c | 59 ---
> hw/virtio/virti
Sorry, any comments for this series? Thanks. :)
B.R.
Yu
On 12/12/2018 9:05 PM, Yu Zhang wrote:
Intel's upcoming processors will extend maximum linear address width to
57 bits, and introduce 5-level paging for CPU. Meanwhile, the platform
will also extend the maximum guest address width for IO
On 13/12/2018 17:26, Tony Krowiak wrote:
If the maximum number of devices allowed on a bus is 1 and a device
which is plugged into the bus is subsequently unplugged, attempting to replug
the device fails with error "Bus 'xxx' does not support hotplugging".
The "error" is detected in the qbus_is_f
On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
> ---
> hw/display/virtio-gpu-pci.c | 14 ++
> hw/display/virtio-vga.c | 1 +
> hw/virtio/virtio-pci.h | 14 --
> 3 files changed, 15 insertions(+), 14 deletio
On 14/12/18 07:29, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
>> On 13/12/18 19:21, Peter Maydell wrote:
>>> On Thu, 13 Dec 2018 at 18:07, Paolo Bonzini wrote:
On 13/12/18 19:01, Peter Maydell wrote:
> I sent a patch to do this a little while back:
> https://patchwork.kerne
On Thu, 13 Dec 2018 at 16:55, Alex Bennée wrote:
>
> When supported by the hardware we can run AA32 guests or even AA64 EL1
> code with AA32 EL0 mode code. Inserting a AA64 break point into AA32
> code tends to break things. This is especially acute with gdb as it
> inserts temporary breakpoints w
Since we're adding checkpatch rules to enforce 4-line multiline comment
format, i.e. with lone /* and */, this script can be run on existing
code so that the comment style does not become inconsistent within a
file.
The alternative to awk-in-a-shell-script could be Perl, which also
supports -i dir
On 2018-12-13 22:00, Juan Quintela wrote:
> Reviewed-by: Laurent Vivier
> Signed-off-by: Juan Quintela
> ---
> hw/virtio/virtio-crypto-pci.c | 14 ++
> hw/virtio/virtio-pci.h| 14 --
> 2 files changed, 14 insertions(+), 14 deletions(-)
>
Reviewed-by: Thomas Huth
On 2018/12/13 22:54, Michael S. Tsirkin wrote:
> On Thu, Dec 13, 2018 at 11:27:24AM +0800, jiangyiwen wrote:
>> On 2018/12/12 21:19, Michael S. Tsirkin wrote:
>>> On Wed, Dec 12, 2018 at 05:54:49PM +0800, jiangyiwen wrote:
Currently vhost-vsock doesn't have any feature bits, so it
don't s
On 2018/12/13 23:34, Stefan Hajnoczi wrote:
> On Thu, Dec 13, 2018 at 11:27:24AM +0800, jiangyiwen wrote:
>> On 2018/12/12 21:19, Michael S. Tsirkin wrote:
>>> On Wed, Dec 12, 2018 at 05:54:49PM +0800, jiangyiwen wrote:
Currently vhost-vsock doesn't have any feature bits, so it
don't supp
On Fri, Dec 14, 2018 at 03:21:22PM +1100, Alexey Kardashevskiy wrote:
> When deciding about the huge DMA window, the typical Linux pseries guest
> uses the maximum allowed RAM size as the upper limit. We did the same
> on QEMU side to match that logic. Now we are going to support a GPU RAM
> pass t
Since we're adding checkpatch rules to enforce 4-line multiline comment
format, i.e. with lone /* and */, this script can be run on existing
code so that the comment style does not become inconsistent within a
file.
The alternative to awk-in-a-shell-script could be Perl, which also
supports -i dir
On Fri, 14 Dec 2018 at 09:16, Li Qiang wrote:
> First of all I want to know does the following error means?
> doesn't it mean "the x86 qtest is ok and aarch64 is not ok"?
>
>
> GTESTER check-qtest-x86_64
> GTESTER check-qtest-aarch64
> vhost-user-test: /tmp/qemu-test/src/util/oslib-posix.c:245
On Wed, 12 Dec 2018 at 11:24, Daniel P. Berrangé wrote:
>
> The following changes since commit bb9bf94b3e8926553290bc9a7cb84315af422086:
>
> Merge remote-tracking branch
> 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2018-12-11
> 19:18:58 +)
>
> are available in the Git
ping
I suppose this one can go in now.
On Wed 14 Nov 2018 03:58:57 PM CET, Alberto Garcia wrote:
> Refcount table entries have a field to store the offset of the
> refcount block. The rest of the bits of the entry are currently
> reserved.
>
> The offset is always taken from the entry using REFT_
Connecting to https://patchew.org/ makes my browser complain:
# patchew.org uses an invalid security certificate.
# The certificate expired on 19 November 2017, 00:27:00 GMT.
# The current time is 14 December 2018, 09:52.
# Error code: SEC_ERROR_EXPIRED_CERTIFICATE
which is a bit odd, given I don
* Wei Wang (wei.w.w...@intel.com) wrote:
> On 12/13/2018 11:45 PM, Dr. David Alan Gilbert wrote:
> > * Wei Wang (wei.w.w...@intel.com) wrote:
> > > The new feature enables the virtio-balloon device to receive hints of
> > > guest free pages from the free page vq.
> > >
> > > A notifier is register
ping
On Thu 22 Nov 2018 04:00:25 PM CET, Alberto Garcia wrote:
> Hi,
>
> a couple of minor fixes for the mirror block job. I don't think these
> bugs can be reproduced at the moment so this shouldn't be 3.1
> material.
>
> Berto
>
> Alberto Garcia (2):
> mirror: Release the dirty bitmap if mirro
On 12/12/18 10:57, David Hildenbrand wrote:
> Let's avoid manually looking up the hotplug handler class. Use the
> existing wrappers instead.
>
> Signed-off-by: David Hildenbrand
> ---
> hw/i386/pc.c | 30 --
> 1 file changed, 8 insertions(+), 22 deletions(-)
>
> dif
On Fri, Dec 14, 2018 at 09:54:06AM +, Peter Maydell wrote:
> Connecting to https://patchew.org/ makes my browser complain:
>
> # patchew.org uses an invalid security certificate.
> # The certificate expired on 19 November 2017, 00:27:00 GMT.
> # The current time is 14 December 2018, 09:52.
> #
On 13/12/2018 18:31, Markus Armbruster wrote:
> Patch created mechanically by rerunning:
>
> $ spatch --sp-file scripts/coccinelle/error_propagate_null.cocci \
> --macro-file scripts/cocci-macro-file.h \
> --dir . --in-place
>
> Whitespace tidied up manually.
>
> Signe
On 13/12/2018 18:58, Markus Armbruster wrote:
> Patch created mechanically by rerunning:
>
> $ spatch --in-place --sp-file scripts/coccinelle/use-error_fatal.cocci \
> --macro-file scripts/cocci-macro-file.h vl.c
>
> Signed-off-by: Markus Armbruster
> ---
> vl.c | 7 ++-
>
On Wed, 12 Dec 2018 at 13:27, Kevin Wolf wrote:
>
> The following changes since commit bb9bf94b3e8926553290bc9a7cb84315af422086:
>
> Merge remote-tracking branch
> 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2018-12-11
> 19:18:58 +)
>
> are available in the Git reposito
> On Dec 14, 2018, at 18:13, Stefan Hajnoczi wrote:
>
> On Fri, Dec 14, 2018 at 09:54:06AM +, Peter Maydell wrote:
>> Connecting to https://patchew.org/ makes my browser complain:
>>
>> # patchew.org uses an invalid security certificate.
>> # The certificate expired on 19 November 2017, 0
On Thu, Dec 13, 2018 at 11:37:37PM +0100, Paolo Bonzini wrote:
> Most files that have TABs only contain a handful of them. Change
> them to spaces so that we don't confuse people.
>
> disas, standard-headers, linux-headers and libdecnumber are imported
> from other projects and probably should be
On 12/14/2018 05:56 PM, Dr. David Alan Gilbert wrote:
* Wei Wang (wei.w.w...@intel.com) wrote:
On 12/13/2018 11:45 PM, Dr. David Alan Gilbert wrote:
* Wei Wang (wei.w.w...@intel.com) wrote:
The new feature enables the virtio-balloon device to receive hints of
guest free pages from the free pag
On Fri, 14 Dec 2018 12:55:20 +1100
Alexey Kardashevskiy wrote:
> SLOF receives a device tree and updates it with various properties
> before switching to the guest kernel and QEMU is not aware of any changes
> made by SLOF. Since there is no real RTAS (QEMU implements it), it makes
> sense to pas
The token field contains the (guest-filled) state of the qtd, which
indicates whenever the other fields are valid or not. So make sure
we read the token first, otherwise we may end up with an stale next
pointer:
(1) ehci reads next
(2) guest writes next
(3) guest writes token
(4) ehci rea
From: Juergen Gross
Don't call xen_be_set_max_grant_refs() in usbback_alloc(), as the
gnttabdev pointer won't be initialised yet. The call can easily be
moved to usbback_connect().
Signed-off-by: Juergen Gross
Message-id: 20181206133923.30105-1-jgr...@suse.com
Signed-off-by: Gerd Hoffmann
---
Open files and directories with O_NOFOLLOW to avoid symlinks attacks.
While being at it also add O_CLOEXEC.
usb-mtp only handles regular files and directories and ignores
everything else, so users should not see a difference.
Because qemu ignores symlinks, carrying out a successful symlink attack
From: Michael Hanselmann
The filename length in MTP metadata is specified by the guest. By
trusting it directly it'd theoretically be possible to get the host to
write memory parts outside the filename buffer into a filename. In
practice though there are usually NUL bytes stopping the string
oper
From: linzhecheng
we should perform these things as same as usb_host_close.
Signed-off-by: linzhecheng
Message-id: 20181130064700.5984-1-linzhech...@huawei.com
[ kraxel: whitespace fixup ]
Signed-off-by: Gerd Hoffmann
---
hw/usb/host-libusb.c | 2 ++
1 file changed, 2 insertions(+)
diff --
The following changes since commit 4f818e7b7f8ecb5c166d093b8859fec2ddeca2ef:
Update version for v3.1.0-rc5 release (2018-12-06 17:07:12 +)
are available in the git repository at:
git://git.kraxel.org/qemu tags/usb-20181214-pull-request
for you to fetch changes up to
On 12/13/18 6:58 PM, Markus Armbruster wrote:
> Patch created mechanically by rerunning:
>
> $ spatch --in-place --sp-file scripts/coccinelle/use-error_fatal.cocci \
> --macro-file scripts/cocci-macro-file.h vl.c
>
> Signed-off-by: Markus Armbruster
Reviewed-by: Philippe Mathie
On 12/13/18 6:31 PM, Markus Armbruster wrote:
> Patch created mechanically by rerunning:
>
> $ spatch --sp-file scripts/coccinelle/error_propagate_null.cocci \
> --macro-file scripts/cocci-macro-file.h \
> --dir . --in-place
>
> Whitespace tidied up manually.
>
> Signe
On 12/10/18 3:08 PM, Gerd Hoffmann wrote:
> There is no reason to allocate mouse events using malloc, we can
> allcoate them from stack instead, save a few cpu cycles and make the
> code more readable with c99 initializers.
Good idea.
>
> Suggested-by: FelixYao
> Signed-off-by: Gerd Hoffmann
On Fri, 14 Dec 2018 at 10:22, Fam Zheng wrote:
> I tried to solve a coming expiration but some misconfiguration and mistakes
> by me stoped it from working today, and I’m unfortunately hitting a rate
> limit of certbot operations. I’ll fix it when the limit is cleared (next
> week, hopefully).
On 12/12/18 11:25 AM, Alex Bennée wrote:
> This is a QEMU specific version of a gitdm config for generating
> reports on the contributor base of the project. I've added enough
> group maps and domain aliases to ensure the current top ten is as
> reflective as it can be. As of this commit running:
>
On Thu, 13 Dec 2018 23:37:37 +0100
Paolo Bonzini wrote:
> Most files that have TABs only contain a handful of them. Change
> them to spaces so that we don't confuse people.
>
> disas, standard-headers, linux-headers and libdecnumber are imported
> from other projects and probably should be exem
The following changes since commit d8d5fefd8657d4f7b380b3a1533340434b5b9def:
Merge remote-tracking branch
'remotes/berrange/tags/qcrypto-next-pull-request' into staging (2018-12-13
18:45:18 +)
are available in the Git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
fo
This commit adds a qemu_init_logging() helper which calls
g_log_set_default_handler() so that glib logs (g_log, g_warning, ...)
are handled similarly to other QEMU logs. This means they will get a
timestamp if timestamps are enabled, and they will go through the
monitor if one is configured.
This c
>>> Indeed, performance traces are important for issues like this.
>>See strace of both FC27 and FC29 attached
>Looks like you traced only the main thread. All the I/O is done in other
>threads.
>These flags would be useful:
>
> strace -o log -f -T -tt
New straces attached with mentioned flag
Hi Alexey,
On 12/14/18 3:58 AM, Alexey Kardashevskiy wrote:
> This adds an accelerator name to the "into mtree -f" to tell the user if
> a particular memory section is registered with the accelerator;
> the primary user for this is KVM and such information is useful
> for debugging purposes.
>
>
On 14/12/2018 11:51, Philippe Mathieu-Daudé wrote:
> On 12/12/18 11:25 AM, Alex Bennée wrote:
>> This is a QEMU specific version of a gitdm config for generating
>> reports on the contributor base of the project. I've added enough
>> group maps and domain aliases to ensure the current top ten is as
This is a QEMU specific version of a gitdm config for generating
reports on the contributor base of the project. I've added enough
group maps and domain aliases to ensure the current top ten is as
reflective as it can be. As of this commit running:
git log --numstat --since "Last Year" | gitdm -
On 12/14/18 1:05 AM, Benjamin Herrenschmidt wrote:
> Note to RiscV folks: You may want to adapt your code to do the same as
> this, esp. afaik, what you do today is endian-broken if host and guest
> endian are different.
Cc'ing the RISC-V list.
> Cheers,
> Ben.
>
> On Fri, 2018-12-14 at 10:58 +
* Wei Wang (wei.w.w...@intel.com) wrote:
> On 12/14/2018 05:56 PM, Dr. David Alan Gilbert wrote:
> > * Wei Wang (wei.w.w...@intel.com) wrote:
> > > On 12/13/2018 11:45 PM, Dr. David Alan Gilbert wrote:
> > > > * Wei Wang (wei.w.w...@intel.com) wrote:
> > > > > The new feature enables the virtio-bal
On Fri, 14 Dec 2018 at 06:29, Markus Armbruster wrote:
>
> Paolo Bonzini writes:
>
> > On 13/12/18 19:21, Peter Maydell wrote:
> >> On Thu, 13 Dec 2018 at 18:07, Paolo Bonzini wrote:
> >>> On 13/12/18 19:01, Peter Maydell wrote:
> I sent a patch to do this a little while back:
> https
On Fri, 30 Nov 2018 at 15:20, Peter Maydell wrote:
>
> This patchset removes the load_image() function, which we noted
> in a comment as being deprecated in 2008 but were still using
> in a handful of places. All the use cases are bugs of some
> kind or another, either straightforward "no length c
On Thu, 22 Nov 2018 at 17:28, Peter Maydell wrote:
>
> This patchset takes three places in generic code which
> use cpu_physical_memory_read(), and changes them to use
> address_space_read() instead.
>
> Changes v1->v2:
> * patches 1, 2 unchanged (and reviewed)
> * patch 3: handle as being NULL
On Thu, 22 Nov 2018 at 13:35, Peter Maydell wrote:
>
> The API of cpu_physical_memory_write_rom() is odd, because it
> takes an AddressSpace, unlike all the other cpu_physical_memory_*
> access functions. We note this oddity as a TODO in the
> docs/devel/loads-stores.rst documentation.
>
> Rename
On 14/12/18 12:32, Peter Maydell wrote:
> On Thu, 22 Nov 2018 at 13:35, Peter Maydell wrote:
>>
>> The API of cpu_physical_memory_write_rom() is odd, because it
>> takes an AddressSpace, unlike all the other cpu_physical_memory_*
>> access functions. We note this oddity as a TODO in the
>> docs/de
On 14/12/18 11:22, Daniel P. Berrangé wrote:
>> crypto/aes.c
>> crypto/desrfb.c
>
> I'd rather like this to be cleaned to finish the job for
> crypto/.
Ok, will do.
Paolo
On Mon, 26 Nov 2018 at 15:03, Anthony PERARD wrote:
>
> On Mon, Nov 19, 2018 at 04:26:58PM +, Peter Maydell wrote:
> > Coverity (CID 796599) points out that xen_pt_setup_vga() trusts
> > the rom->size field in the BIOS ROM from a PCI passthrough VGA
> > device, and uses it as an index into the
On 13.12.2018 15:20, Kevin Wolf wrote:
> Am 13.12.2018 um 12:07 hat Denis Plotnikov geschrieben:
>> On 12.12.2018 15:24, Kevin Wolf wrote:
>>> Am 11.12.2018 um 17:55 hat Denis Plotnikov geschrieben:
> Why involve the AioContext at all? This could all be kept at the
> BlockBackend level wi
* Daniel Henrique Barboza (danielhb...@gmail.com) wrote:
> At this moment, QEMU attempts to create/load/delete snapshots
> by using either an ID (id_str) or a name. The problem is that the code
> isn't consistent of whether the entered argument is an ID or a name,
> causing unexpected behaviors.
>
On Thu, 13 Dec 2018 11:26:42 -0500
Tony Krowiak wrote:
> If the maximum number of devices allowed on a bus is 1 and a device
> which is plugged into the bus is subsequently unplugged, attempting to replug
> the device fails with error "Bus 'xxx' does not support hotplugging".
> The "error" is det
On 12/13/2018 04:01 PM, Peter Maydell wrote:
On Thu, 13 Dec 2018 at 17:57, Wainer dos Santos Moschetta
wrote:
Eduardo Habkost pointed out a malformed block of comments on my
patch [1] that I had ran checkpatch.pl and no warn/error was
reported. Then I realized the script does not catch such a
On Thu, Dec 13, 2018 at 09:03:23PM +0100, Thomas Huth wrote:
> On 2018-12-13 13:42, Kashyap Chamarthy wrote:
> > Also fix the wrong spelling of it: s/cpu-add/cpu_add/
> >
> > Signed-off-by: Kashyap Chamarthy
> > ---
> > qemu-deprecated.texi | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deleti
I want to make it consistent but I'm note sure I understand all aspects
of current state and legacy clients we need to support.
The initial idea was to have single function blk_lookup(char* name) and
search in all namespaces internally as they are guaranteed to have no
intersection. This will
Our command line interface is really quite overcrowded, we should avoid
duplicated options that do the same thing in just a slightly different
way. "-accel hax" is shorter and more generic that "-enable-hax", so
there is really no real usage for the latter option. "-enable-hax" has
been deprecated
Am 14.12.2018 um 11:59 hat De Backer, Fred (Nokia - BE/Antwerp) geschrieben:
> >>> Indeed, performance traces are important for issues like this.
> >>See strace of both FC27 and FC29 attached
>
> >Looks like you traced only the main thread. All the I/O is done in other
> >threads.
> >These flags
Peter Maydell writes:
> On Fri, 14 Dec 2018 at 06:29, Markus Armbruster wrote:
>>
>> Paolo Bonzini writes:
>>
>> > On 13/12/18 19:21, Peter Maydell wrote:
>> >> On Thu, 13 Dec 2018 at 18:07, Paolo Bonzini wrote:
>> >>> On 13/12/18 19:01, Peter Maydell wrote:
>> I sent a patch to do this a
On 12/14/18 1:21 PM, Thomas Huth wrote:
> Our command line interface is really quite overcrowded, we should avoid
> duplicated options that do the same thing in just a slightly different
> way. "-accel hax" is shorter and more generic that "-enable-hax", so
> there is really no real usage for the l
This is still reproducible on git master:
(sid-sh4-sbuild)root@nofan:/# autogen
Unhandled trap: 0x180
pc=0x7f4da99e sr=0x pr=0x7f3bfc74 fpscr=0x0008
spc=0x ssr=0x gbr=0x7f114320 vbr=0x
sgr=0x dbr=0x delayed_pc=0x7f4da960 fpul=0x0003
r0=0x7ffc
This has been fixed now and Java works fine again on qemu-sh4 on git
master:
(sid-sh4-sbuild)root@nofan:/# java --version
openjdk 10 2018-03-20
OpenJDK Runtime Environment (build 10+46-Debian-5)
OpenJDK Zero VM (build 10+46-Debian-5, interpreted mode)
(sid-sh4-sbuild)root@nofan:/#
** Changed in:
This still reproduces on git master:
(sid-sh4-sbuild)root@nofan:/# gcc setcontext.c -o setcontext -lpthread
(sid-sh4-sbuild)root@nofan:/# ./setcontext
Unhandled trap: 0x180
pc=0x7f68e99e sr=0x pr=0x00400750 fpscr=0x0008
spc=0x ssr=0x gbr=0x7f7a2de8 vbr=0x
sgr=0
>Of course, we should also think about the other problem you mentioned, related
>to copying a smaller image to a larger block device. Does this require zeroing
>the parts after the image or should we leave them alone?
>
>I'd tend to say that since you're passing the whole block device as a target
On Fri, Dec 14, 2018 at 07:07:44AM +, Gonglei (Arei) wrote:
>
> > -Original Message-
> > From: Juan Quintela [mailto:quint...@redhat.com]
> > Sent: Friday, December 14, 2018 5:01 AM
> > To: qemu-devel@nongnu.org
> > Cc: Michael S. Tsirkin ; Thomas Huth ;
> > Gerd Hoffmann ; Gonglei (Ar
On Fri, 14 Dec 2018 at 12:31, Markus Armbruster wrote:
> Peter Maydell writes:
> > On Fri, 14 Dec 2018 at 06:29, Markus Armbruster wrote:
> > I have to admit I never really understood what tweak
> > you wanted making to the commit message. I'm happy
> > to make it clearer: do you want to suggest
On Fri, Dec 14, 2018 at 05:43:28PM +0800, jiangyiwen wrote:
> On 2018/12/13 22:54, Michael S. Tsirkin wrote:
> > On Thu, Dec 13, 2018 at 11:27:24AM +0800, jiangyiwen wrote:
> >> On 2018/12/12 21:19, Michael S. Tsirkin wrote:
> >>> On Wed, Dec 12, 2018 at 05:54:49PM +0800, jiangyiwen wrote:
> C
On Wed, 12 Dec 2018 at 09:13, Thomas Huth wrote:
>
> Hi Peter,
>
> the following changes since commit bb9bf94b3e8926553290bc9a7cb84315af422086:
>
> Merge remote-tracking branch
> 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2018-12-11
> 19:18:58 +)
>
> are available in
On Wed, 12 Dec 2018 09:11:15 -0500
"Jason J. Herne" wrote:
> Now that we have a Channel I/O library let's modify virtio boot code to
> make use of it for running channel programs.
>
> Signed-off-by: Jason J. Herne
> ---
> pc-bios/s390-ccw/virtio.c | 21 ++---
> 1 file changed,
The time2tod() function tries to deal with the 9 uppermost bits in the
time value, but uses the wrong mask for this: 0xff80 should
be used instead of 0xff10 here.
Fixes: 14055ce53c2d901d826ffad7fb7d6bb8ab46bdfd
Signed-off-by: Thomas Huth
---
include/hw/s390x/tod.h | 2 +-
On Fri, Dec 14, 2018 at 12:52:34PM +, De Backer, Fred (Nokia - BE/Antwerp)
wrote:
> >Of course, we should also think about the other problem you mentioned,
> >related to copying a smaller image to a larger block device. Does this
> >require zeroing the parts after the image or should we leav
Add some more functions that will be used in memory-device context.
range_init(): Init using lower bound and size, check for validity
range_init_nofail(): Init using lower bound and size, validity asserted
range_size(): Extract the size of a range
range_overlaps_range(): Check for overlaps of two
These are the two leftovers from
[PATCH v3 0/7] qapi/range/memory-device: fixes and cleanups
The remaining patches extent the QEMU range code and rewrite
memory-device code to make use of it.
v34 -> v5:
- "memory-device: rewrite address assignment using ranges"
-- Squash to error pathes that
On 14.12.18 14:08, Thomas Huth wrote:
> The time2tod() function tries to deal with the 9 uppermost bits in the
> time value, but uses the wrong mask for this: 0xff80 should
> be used instead of 0xff10 here.
>
> Fixes: 14055ce53c2d901d826ffad7fb7d6bb8ab46bdfd
> Signed-off-by
Let's rewrite it properly using ranges. This fixes certain overflows that
are right now possible. E.g.
qemu-system-x86_64 -m 4G,slots=20,maxmem=40G -M pc \
-object memory-backend-file,id=mem1,share,mem-path=/dev/zero,size=2G
-device pc-dimm,memdev=mem1,id=dimm1,addr=-0x4000
Now proper
On 14.12.2018 14:08, Thomas Huth wrote:
> The time2tod() function tries to deal with the 9 uppermost bits in the
> time value, but uses the wrong mask for this: 0xff80 should
> be used instead of 0xff10 here.
>
> Fixes: 14055ce53c2d901d826ffad7fb7d6bb8ab46bdfd
Can you a
On Fri, Dec 14, 2018 at 01:26:59PM +0100, Kevin Wolf wrote:
> Am 14.12.2018 um 11:59 hat De Backer, Fred (Nokia - BE/Antwerp) geschrieben:
> > >>> Indeed, performance traces are important for issues like this.
> > >>See strace of both FC27 and FC29 attached
> >
> > >Looks like you traced only the
On 2018-12-14 14:15, Christian Borntraeger wrote:
>
>
> On 14.12.2018 14:08, Thomas Huth wrote:
>> The time2tod() function tries to deal with the 9 uppermost bits in the
>> time value, but uses the wrong mask for this: 0xff80 should
>> be used instead of 0xff10 here.
>>
>>
On 14.12.2018 14:23, Thomas Huth wrote:
> On 2018-12-14 14:15, Christian Borntraeger wrote:
>>
>>
>> On 14.12.2018 14:08, Thomas Huth wrote:
>>> The time2tod() function tries to deal with the 9 uppermost bits in the
>>> time value, but uses the wrong mask for this: 0xff80 should
>>>
1 - 100 of 235 matches
Mail list logo
