Hello Philippe,
+-- On Sun, 12 Nov 2017, Philippe Mathieu-Daudé wrote --+
| I'd rather use:
|
|"highbank: bad write offset 0x%" HWADDR_PRIx "\n", offset);
Sent revised patch v2. Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE
On 11/10/2017 08:53 PM, Emilio G. Cota wrote:
> 55c3cee ("qom: Introduce CPUClass.tcg_initialize", 2017-10-24)
> introduces a per-CPUClass bool that we check so that the target CPU
> is initialized for TCG only once. This works well except when
> we end up creating more than one CPUClass, in which
On 11/11/2017 19:59, Stefan Priebe - Profihost AG wrote:
> Hello,
>
> Am 10.11.2017 um 05:18 schrieb Jason Wang:
>>
>>
>> On 2017年11月08日 19:22, Jason Wang wrote:
>>>
>>>
>>> On 2017年11月08日 18:46, Paolo Bonzini wrote:
On 08/11/2017 09:21, Jason Wang wrote:
>
> On 2017年11月08日 17:05, Ste
On 13/11/2017 02:45, gengdongjiu wrote:
> On 2017/11/10 19:32, Paolo Bonzini wrote:
>> On 10/11/2017 20:19, Dongjiu Geng wrote:
>>> +typedef struct HWPoisonPage {
>>> +ram_addr_t ram_addr;
>>> +QLIST_ENTRY(HWPoisonPage) list;
>>> +} HWPoisonPage;
>>> +
>>
>> Is this actually needed outside
On Mon, Nov 13, 2017 at 04:56:01PM +1100, David Gibson wrote:
> On Fri, Nov 03, 2017 at 08:01:52PM +0800, Liu, Yi L wrote:
> > From: Peter Xu
> >
> > AddressSpaceOps is similar to MemoryRegionOps, it's just for address
> > spaces to store arch-specific hooks.
> >
> > The first hook I would like
On 2017/11/13 16:27, Paolo Bonzini wrote:
>> If you think this structure should be added in accel/kvm/kvm-all.c, I will
>> move it.
> It can be done later; but if you have to send a v13 series, I would be
> grateful if you included this change as well.
Ok, got it, thanks Paolo.
>
> Paolo
>
The statement being removed doesn't change anything as virtio PCI devices
already
have Subsystem Vendor ID set to pci_default_sub_vendor_id (0x1af4), same as
Vendor
ID. And the Virtio spec does not require the two to be equal, either:
"The PCI Subsystem Vendor ID and the PCI Subsystem Device I
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> > From: "David Hildenbrand"
> > On 02.11.2017 12:08, Paolo Bonzini wrote:
> > > On 31/10/2017 12:26, Pavel Dovgalyuk wrote:
> > >> From: Alex Bennée
> > >>
> > >> Now the only real need to hold the BQL is for when we sleep on the
> > >> cpu->ha
On 09/11/2017 17:50, Cornelia Huck wrote:
On Tue, 7 Nov 2017 18:24:34 +0100
Pierre Morel wrote:
Enhance the fault detection, correction of the fault reporting.
Signed-off-by: Pierre Morel
Reviewed-by: Yi Min Zhao
---
hw/s390x/s390-pci-inst.c | 41 -
On 09/11/2017 17:51, Cornelia Huck wrote:
On Tue, 7 Nov 2017 18:24:35 +0100
Pierre Morel wrote:
Enhance the fault detection, correction of the fault reporting.
Basically the same comments as for the previous patch (but looks good
in general).
thanks I will process it the same way as patch
On 10/11/2017 10:51, Cornelia Huck wrote:
On Fri, 10 Nov 2017 17:40:12 +0800
Yi Min Zhao wrote:
在 2017/11/10 上午3:23, Cornelia Huck 写道:
On Tue, 7 Nov 2017 18:24:38 +0100
Pierre Morel wrote:
Let's move the memory region write from pcistg into a dedicated
function.
This allows us to prepar
The pixman submodule has been removed in commit c12b6d70e384c769ca372e1,
so there is no need anymore to delete pixman/.git while building a
release tarball.
Signed-off-by: Thomas Huth
---
scripts/make-release | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/make-releas
On Mon, Nov 13, 2017 at 09:45:58AM +0100, Ladi Prosek wrote:
> The statement being removed doesn't change anything as virtio PCI devices
> already
> have Subsystem Vendor ID set to pci_default_sub_vendor_id (0x1af4), same as
> Vendor
> ID. And the Virtio spec does not require the two to be equal,
On 09/11/2017 19:55, Philippe Mathieu-Daudé wrote:
On 11/09/2017 01:38 PM, Cornelia Huck wrote:
On Tue, 7 Nov 2017 18:24:33 +0100
Pierre Morel wrote:
There are two places where the same endianness conversion
is done.
Let's factor this out into a static function.
Signed-off-by: Pierre Morel
On 09/11/2017 19:55, Philippe Mathieu-Daudé wrote:
On 11/09/2017 01:38 PM, Cornelia Huck wrote:
On Tue, 7 Nov 2017 18:24:33 +0100
Pierre Morel wrote:
There are two places where the same endianness conversion
is done.
Let's factor this out into a static function.
Signed-off-by: Pierre Morel
On 10/11/2017 10:51, Cornelia Huck wrote:
On Fri, 10 Nov 2017 17:40:12 +0800
Yi Min Zhao wrote:
在 2017/11/10 上午3:23, Cornelia Huck 写道:
On Tue, 7 Nov 2017 18:24:38 +0100
Pierre Morel wrote:
Let's move the memory region write from pcistg into a dedicated
function.
This allows us to prepar
On 09/11/2017 17:51, Cornelia Huck wrote:
On Tue, 7 Nov 2017 18:24:35 +0100
Pierre Morel wrote:
Enhance the fault detection, correction of the fault reporting.
Basically the same comments as for the previous patch (but looks good
in general).
thanks I will process it the same way as patch
Triaging old bug tickets... has this ever been fixed, thus could we
close this ticket nowadays? Or is there something left to do here?
** Changed in: qemu
Status: Confirmed => Incomplete
** Changed in: qemu
Assignee: Anthony Liguori (anthony-codemonkey) => (unassigned)
--
You receiv
On 13.11.2017 10:43, no-re...@patchew.org wrote:
> Hi,
>
> This series failed automatic build test. Please find the testing commands and
> their output below. If you have docker installed, you can probably reproduce
> it
> locally.
>
> Subject: [Qemu-devel] [PATCH] scripts/make-release: No need
On Mon, 13 Nov 2017 16:51:03 +1100
David Gibson wrote:
> On Fri, Nov 10, 2017 at 03:20:07PM +, Cédric Le Goater wrote:
> > Signed-off-by: Cédric Le Goater
> > ---
> > hw/ppc/spapr.c | 16 +++-
> > 1 file changed, 15 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/ppc/spapr
On 13 November 2017 at 07:13, Jason Wang wrote:
>
>
> On 2017年11月06日 21:28, Jens Freimann wrote:
>>
>> This fixes coverity issue CID1005339.
>>
>> Make sure that saddr is not used uninitialized if the
>> mcast parameter is NULL.
>>
>> Cc: qemu-sta...@nongnu.org
>> Reported-by: Peter Maydell
>> Si
On 13 November 2017 at 07:14, Thomas Huth wrote:
> By the way, before everybody now introduces "2.12" machine types ... is
> there already a consensus that the next version will be "2.12" ?
>
> A couple of months ago, we discussed that we could maybe do a 3.0 after
> 2.11, e.g. here:
>
> https://
On Fri 10 Nov 2017 04:19:34 PM CET, Stefan Hajnoczi wrote:
> I/O requests hang after stop/cont commands at least since QEMU 2.10.0
> with -drive iops=100:
>
> (guest)$ dd if=/dev/zero of=/dev/vdb oflag=direct count=1000
> (qemu) stop
> (qemu) cont
> ...I/O is stuck...
>
> This happens becau
On 2017年11月13日 17:51, Peter Maydell wrote:
On 13 November 2017 at 07:13, Jason Wang wrote:
On 2017年11月06日 21:28, Jens Freimann wrote:
This fixes coverity issue CID1005339.
Make sure that saddr is not used uninitialized if the
mcast parameter is NULL.
Cc: qemu-sta...@nongnu.org
Reported-by
"stm32-p103" is not a board model supported by upstream QEMU. Presumably
you're using a fork of QEMU -- you should ask whoever is responsible for
that fork about it.
For the second command line -- is the binary you're trying to run built for the
stellaris board model you're trying to run it on?
On 11/13/2017 10:53 AM, Peter Maydell wrote:
> On 13 November 2017 at 07:14, Thomas Huth wrote:
>> By the way, before everybody now introduces "2.12" machine types ... is
>> there already a consensus that the next version will be "2.12" ?
>>
>> A couple of months ago, we discussed that we could ma
On 8 November 2017 at 19:20, Stefan Hajnoczi wrote:
> The following changes since commit b0fbe46ad82982b289a44ee2495b59b0bad8a842:
>
> Update version for v2.11.0-rc0 release (2017-11-07 16:05:28 +)
>
> are available in the git repository at:
>
> git://github.com/stefanha/qemu.git tags/bloc
Pavel Dovgalyuk writes:
>> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
>> > From: "David Hildenbrand"
>> > On 02.11.2017 12:08, Paolo Bonzini wrote:
>> > > On 31/10/2017 12:26, Pavel Dovgalyuk wrote:
>> > >> From: Alex Bennée
>> > >>
>> > >> Now the only real need to hold the BQL is for w
On Mon, Nov 13, 2017 at 04:56:01PM +1100, David Gibson wrote:
> On Fri, Nov 03, 2017 at 08:01:52PM +0800, Liu, Yi L wrote:
> > From: Peter Xu
> >
> > AddressSpaceOps is similar to MemoryRegionOps, it's just for address
> > spaces to store arch-specific hooks.
> >
> > The first hook I would like
On 13 November 2017 at 10:03, Cédric Le Goater wrote:
> One of the sweeping change for 3.0 could be to stop to maintaining
> migration compatibility with older versions (2.x). Even if the
> feature is really a must have in some cluster environment, the
> code (and the developer) is starting to suf
On Fri, Nov 10, 2017 at 04:21:05PM -0600, Eric Blake wrote:
> On 11/10/2017 04:13 PM, Max Reitz wrote:
> > We have a clear replacement, so let's deprecate it.
> >
> > Signed-off-by: Max Reitz
> > ---
> > qapi/block-core.json | 4 ++--
> > block.c | 4
> > qemu-doc.texi|
On 13.11.2017 10:53, Peter Maydell wrote:
> On 13 November 2017 at 07:14, Thomas Huth wrote:
>> By the way, before everybody now introduces "2.12" machine types ... is
>> there already a consensus that the next version will be "2.12" ?
>>
>> A couple of months ago, we discussed that we could maybe
Ping for comments, thanks.
On 11/03/2017 04:13 PM, Wei Wang wrote:
Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_VQ feature indicates the
support of reporting hints of guest free pages to the host via
virtio-balloon. The host requests the guest to report the free pages by
sending commands via th
On Mon, Nov 13, 2017 at 10:21:45AM +0100, Thomas Huth wrote:
> The pixman submodule has been removed in commit c12b6d70e384c769ca372e1,
> so there is no need anymore to delete pixman/.git while building a
> release tarball.
>
> Signed-off-by: Thomas Huth
Reviewed-by: Gerd Hoffmann
On 11/11/17 16:25, Marcel Apfelbaum wrote:
> Currently there is no MMIO range over 4G
> reserved for PCI hotplug. Since the 32bit PCI hole
> depends on the number of cold-plugged PCI devices
> and other factors, it is very possible is too small
> to hotplug PCI devices with large BARs.
>
> Fix it
On 13/11/2017 11:14, Alex Bennée wrote:
>
> Pavel Dovgalyuk writes:
>
>>> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
From: "David Hildenbrand"
On 02.11.2017 12:08, Paolo Bonzini wrote:
> On 31/10/2017 12:26, Pavel Dovgalyuk wrote:
>> From: Alex Bennée
>>
>> Now
On 8 November 2017 at 12:37, Philippe Mathieu-Daudé wrote:
> On 11/07/2017 05:46 PM, Emilio G. Cota wrote:
>> Fixes the following warning when compiling with gcc 5.4.0 with -O1
>> optimizations and --enable-debug:
>>
>> target/arm/translate-a64.c: In function ‘aarch64_tr_translate_insn’:
>> target
On 13 November 2017 at 06:26, P J P wrote:
> From: Prasad J Pandit
>
> An 'offset' parameter sent to highbank register r/w functions
> could be greater than number(NUM_REGS=0x200) of hb registers,
> leading to an OOB access issue. Add check to avoid it.
>
> Reported-by: Moguofang (Dennis mo)
> S
Richard Henderson writes:
> ---
> disas.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/disas.c b/disas.c
> index d6a1eb9c8e..69069a85ca 100644
> --- a/disas.c
> +++ b/disas.c
> @@ -231,7 +231,7 @@ void target_disas(FILE *out, CPUState *cpu, target_ulong
> code,
>
On 13 November 2017 at 05:55, Subbaraya Sundeep wrote:
> Voluntarily add myself as maintainer for Smartfusion2
>
> Signed-off-by: Subbaraya Sundeep
> Reviewed-by: Alistair Francis
> Reviewed-by: Philippe Mathieu-Daudé
> ---
> v2:
> reframed commit message as per Alistair's comment.
>
Richard Henderson writes:
"...and enable it for the 'any' CPUs used by linux-user"?
Otherwise:
Reviewed-by: Alex Bennée
> Signed-off-by: Richard Henderson
> ---
> target/arm/cpu.h | 1 +
> linux-user/elfload.c | 9 +
> target/arm/cpu.c | 1 +
> target/arm/cpu64.c | 1 +
>
12.11.2017 04:39, Eric Blake wrote:
If a server fails a read, for example with EIO, but the connection
is still live, then we would crash trying to print a non-existent
error message. Bug introduced in commit f140e300.
Signed-off-by: Eric Blake
---
block/nbd-client.c | 4 ++--
1 file change
On 10 November 2017 at 19:53, Emilio G. Cota wrote:
> Some MachineClass changes to fix TCG initialization of some
> ARM boards for 2.11. This was originally reported by Thomas Huth in [1],
> where Peter suggested a way to fix it. Further discussion in
> another thread [2] followed up on this.
>
>
Hi Peter,
On 11/13/2017 01:22 AM, Peter Xu wrote:
On Fri, Nov 10, 2017 at 06:35:16PM -0200, Daniel Henrique Barboza wrote:
When migrating a VM with 'migrate_set_capability postcopy-ram on'
a postcopy_state is set during the process, ending up with the
state POSTCOPY_INCOMING_END when the migrat
On 9 November 2017 at 07:52, Richard Henderson
wrote:
> One build fix for mingw cross-compiling, one feature regression fix.
>
>
> r~
>
>
> The following changes since commit b0fbe46ad82982b289a44ee2495b59b0bad8a842:
>
> Update version for v2.11.0-rc0 release (2017-11-07 16:05:28 +)
>
> are
On Mon, 13 Nov 2017 10:03:37 +0100
Pierre Morel wrote:
> On 09/11/2017 17:50, Cornelia Huck wrote:
> > On Tue, 7 Nov 2017 18:24:34 +0100
> > Pierre Morel wrote:
> >> +case PCI_ROM_SLOT:
> >
> > So, will this be filled in a later patch? (Reading from the top.)
>
> No it will not it is
On Mon, 13 Nov 2017 10:39:50 +0100
Pierre Morel wrote:
> On 10/11/2017 10:51, Cornelia Huck wrote:
> > On Fri, 10 Nov 2017 17:40:12 +0800
> > Yi Min Zhao wrote:
> >
> >> 在 2017/11/10 上午3:23, Cornelia Huck 写道:
> >>> On Tue, 7 Nov 2017 18:24:38 +0100
> >>> Pierre Morel wrote:
> >>>
> >
On Wed, Nov 8, 2017 at 3:28 PM, Mihail Abakumov
wrote:
> Ladi Prosek писал 2017-11-08 16:43:
>
>> On Wed, Nov 8, 2017 at 12:54 PM, Mihail Abakumov
>> wrote:
>>>
>>> Ladi Prosek писал 2017-11-06 18:15:
>>>
>>> In your case windbg does not send packets, more specifically, does not
>>> continue to d
From: Zhu Yijun
Dig out reserved memory holes and collect scattered RAM memory
regions by adding mem_list member in arm_boot_info struct.
Signed-off-by: Zhu Yijun
---
hw/arm/boot.c| 8
hw/arm/virt.c| 101 ++-
include/hw/arm
From: Zhu Yijun
With kernel 4.11, iommu/smmu will populate the MSI IOVA reserved window and
PCI reserved window which has to be excluded from Guest iova allocations.
And on certain HiSilicon platforms (hip06/hip07), the GIC ITS and PCIe RC
deviates from the standard implementation will reserve
From: Zhu Yijun
With kernel 4.11, iommu/smmu will populate the MSI IOVA reserved window and
PCI reserved window which has to be excluded from Guest iova allocations.
However, If it falls within the Qemu default virtual memory address space,
then reserved regions may get allocated for a Guest VF
"Dr. David Alan Gilbert" writes:
> * Vadim Galitsyn (vadim.galit...@profitbricks.com) wrote:
>> Hi Guys,
>>
>> This thread is a continuation of discussion started in
>> http://lists.nongnu.org/archive/html/qemu-devel/2017-02/msg03182.html.
>>
>> This series introduces ‘writeconfig’ command supp
On Sun, Nov 12, 2017 at 08:30:25PM +0100, Jindrich Makovicka wrote:
> With SDL 2.0.6, calling SDL_ShowWindow during SDL_WINDOWEVENT_HIDDEN
> blocks all subsequent display updates.
>
> Instead of trying to override the change, just update the scon->hidden
> flag.
Has for me the side effect that so
On Mon, Nov 13, 2017 at 01:39:14PM +0100, Gerd Hoffmann wrote:
> On Sun, Nov 12, 2017 at 08:30:25PM +0100, Jindrich Makovicka wrote:
> > With SDL 2.0.6, calling SDL_ShowWindow during SDL_WINDOWEVENT_HIDDEN
> > blocks all subsequent display updates.
> >
> > Instead of trying to override the change,
Hi Peter,
On 09/10/2017 19:47, Peter Maydell wrote:
> On 1 September 2017 at 18:21, Eric Auger wrote:
>> The VirtMachineState contains some dt phandles that will be used
>> in some node creation functions. For instance we plan to use the
>> PCI host controller phandle in the smmu node creation fu
On 10/13/2017 4:26 PM, Eric Blake wrote:
[adding Markus, and block list]
On 10/13/2017 09:16 AM, Alberto Garcia wrote:
On Mon 02 Oct 2017 04:33:28 PM CEST, Pradeep Jagadeesh wrote:
This patch factors out code to use the ThrottleLimits
structure.
{ 'struct': 'BlockIOThrottle',
- 'data': {
On 11/11/2017 17:25, Marcel Apfelbaum wrote:
Currently there is no MMIO range over 4G
reserved for PCI hotplug. Since the 32bit PCI hole
depends on the number of cold-plugged PCI devices
and other factors, it is very possible is too small
to hotplug PCI devices with large BARs.
Fix it by reservi
On 13 November 2017 at 13:00, Auger Eric wrote:
> On 09/10/2017 19:47, Peter Maydell wrote:
>> More generally, why is sysbus-fdt involved in this at all?
>> I expected that instantiating and wiring up the SMMU would
>> be the job of hw/arm/virt.c, like any other device we
>> might have on the boar
On 11/13/2017 08:17 AM, Gonglei (Arei) wrote:
>>> +struct virtio_crypto_cipher_session_req {
>>> +/* Device-readable part */
>>> +struct virtio_crypto_cipher_session_para para;
>>> +/* The cipher key */
>>> +u8 cipher_key[keylen];
>>> +
>> Is there a limit to the size of chiper_ke
On 9 November 2017 at 15:32, Cornelia Huck wrote:
> The following changes since commit b0fbe46ad82982b289a44ee2495b59b0bad8a842:
>
> Update version for v2.11.0-rc0 release (2017-11-07 16:05:28 +)
>
> are available in the git repository at:
>
> git://github.com/cohuck/qemu tags/s390x-201711
On Mon, Nov 13, 2017 at 1:59 PM, Gerd Hoffmann wrote:
> On Mon, Nov 13, 2017 at 01:39:14PM +0100, Gerd Hoffmann wrote:
>> On Sun, Nov 12, 2017 at 08:30:25PM +0100, Jindrich Makovicka wrote:
>> > With SDL 2.0.6, calling SDL_ShowWindow during SDL_WINDOWEVENT_HIDDEN
>> > blocks all subsequent display
Fails scripts/checkpatch.pl (trailing whitespace on several lines).
On Sun, Nov 12, 2017 at 08:30:29PM +0100, Jindrich Makovicka wrote:
> This patch fixes mouse positioning with -device usb-tablet and fullscreen
> or resized window.
Fails checkpatch too (long lines).
Also: can you add a "Fixes: 46522a82236ea0cf9011b89896d2d8f8ddaf2443"
line (that is the commit wh
Thanks for the Detail Robin!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
Status in QEMU:
Invalid
Status in linux package i
On 8 November 2017 at 15:32, Alex Bennée wrote:
> We are still seeing signals during translation time when we walk over
> a page protection boundary. This expands the check to ensure the host
> PC is inside the code generation buffer. The original suggestion was
> to check versus tcg_ctx.code_gen_
On Thu, Nov 9, 2017 at 5:54 PM, Cédric Le Goater wrote:
> On 11/08/2017 04:24 AM, Joel Stanley wrote:
>> --- a/hw/misc/aspeed_sdmc.c
>> +++ b/hw/misc/aspeed_sdmc.c
>> @@ -18,7 +18,6 @@
>>
>> /* Protection Key Register */
>> #define R_PROT(0x00 / 4)
>> -#define PROT_KEY_UNLOCK
The ASPEED hardware contains a lock register for the SCU that disables
any writes to the SCU when it is locked. The machine comes up with the
lock enabled, but on all known hardware u-boot will unlock it and leave
it unlocked when loading the kernel.
This means the kernel expects the SCU to be unl
Hi,
> if (!gui_grab && (qemu_input_is_absolute() || absolute_enabled)) {
> absolute_mouse_grab(scon);
> }
Can you please add a comment here describing why this is done?
>From the code alone it isn't obvious that this is a workaround
for a SDL bug.
> +scon-
I looked a bit more at the sanitizers source code, to understand the
differences between arm and aarch64. And it turns out that on aarch64,
we have:
sanitizer_common/sanitizer_syscall_linux_aarch64.inc:
133 // Helper function used to avoid cobbler errno.
134 bool internal_iserror(uptr retv
I also looked at QEMU's code, and I am suprised that do_syscall()
returns the value of errno rather than the return code from the syscall.
So for instance, if clone() fails, do_syscall() returns
get_errno(do_fork(...)) instead of -1. I thought the target code expects
-1 in case of failure, but I'm
On Sun, Nov 12, 2017 at 08:30:24PM +0100, Jindrich Makovicka wrote:
> Hi,
>
> here is an identical patchset with Signed-off-by.
Please post a new version without reply-to.
Queued up four patches:
sdl2: Do not leave grab when fullscreen
sdl2: Fix dead keyboard after fullsceen
sdl2: Use the
Hi Peter,
On 13/11/2017 14:08, Peter Maydell wrote:
> On 13 November 2017 at 13:00, Auger Eric wrote:
>> On 09/10/2017 19:47, Peter Maydell wrote:
>>> More generally, why is sysbus-fdt involved in this at all?
>>> I expected that instantiating and wiring up the SMMU would
>>> be the job of hw/arm
Hi,
> >> Have a slightly older SDL version (2.0.3). Do you see that effect with
> >> 2.0.6 too?
> >
> > Oh, and I've just seen the current code has been added as attempt to
> > workaround that bug, see commit d3f3a0f453ea590be529079ae214c200bb5ecc1a.
> >
> > Hmm. Seems we are trading one issue
Hello Halil,
Thanks for your feedback.
>
> On 11/13/2017 08:17 AM, Gonglei (Arei) wrote:
> >>> +struct virtio_crypto_cipher_session_req {
> >>> +/* Device-readable part */
> >>> +struct virtio_crypto_cipher_session_para para;
> >>> +/* The cipher key */
> >>> +u8 cipher_key[keyl
On 13 November 2017 at 13:37, Auger Eric wrote:
> On 13/11/2017 14:08, Peter Maydell wrote:
>> Not being able to conveniently wire up a sysbus device on the
>> command line or pass it options are general problems. I don't
>> think the SMMU is a special case that should work around these
>> general
Hmm, the do_fork() code is a bit inconsistent there. Generally in linux-user/
functions should either:
(1) return -1 with host errno set to a host errno; the caller then must use
get_errno() to convert to the negative-target-errno that we need to return from
do_syscall()
(2) return negative-targ
On 9 November 2017 at 16:59, Eric Blake wrote:
> The following changes since commit b0fbe46ad82982b289a44ee2495b59b0bad8a842:
>
> Update version for v2.11.0-rc0 release (2017-11-07 16:05:28 +)
>
> are available in the git repository at:
>
> git://repo.or.cz/qemu/ericb.git tags/pull-nbd-201
Hi,
On 13/11/2017 14:44, Peter Maydell wrote:
> On 13 November 2017 at 13:37, Auger Eric wrote:
>> On 13/11/2017 14:08, Peter Maydell wrote:
>>> Not being able to conveniently wire up a sysbus device on the
>>> command line or pass it options are general problems. I don't
>>> think the SMMU is a
Thomas Huth writes:
> The qdev_unplug() function contains a g_assert(hotplug_ctrl) statement,
> so QEMU crashes when the user tries to device_add + device_del a device
> that does not have a corresponding hotplug controller. This could be
> provoked for a couple of devices in the past (see commit
On Wed 08 Nov 2017 03:33:54 PM CET, Kevin Wolf wrote:
>> This patch makes bdrv_close() do the full uninitialization process in
>> all cases. This fixes the problem with corrupted images and still
>> works fine with freshly created BDSs.
>>
>> Signed-off-by: Alberto Garcia
>
> This doesn't apply c
On Fri 10 Nov 2017 11:21:27 PM CET, Max Reitz wrote:
> By the way, I just noticed that this test tests that
> x-blockdev-remove-medium and x-blockdev-insert-medium do not destroy
> throttling information -- which is exactly why those commands had been
> declared experimental in the first place.
O
From: "Emilio G. Cota"
max_cpus needs to be an upper bound on the number of vCPUs
initialized; otherwise TCG region initialization breaks.
Some boards initialize a hard-coded number of vCPUs, which is not
captured by the global max_cpus and therefore breaks TCG initialization.
Fix it by adding t
From: "Emilio G. Cota"
Just like the zcu102, the ep108 can instantiate several CPUs.
Signed-off-by: Emilio G. Cota
Reviewed-by: Alistair Francis
Message-id: 1510343626-25861-5-git-send-email-c...@braap.org
Signed-off-by: Peter Maydell
---
hw/arm/xlnx-zcu102.c | 1 +
1 file changed, 1 inserti
From: "Emilio G. Cota"
Fixes the following warning when compiling with gcc 5.4.0 with -O1
optimizations and --enable-debug:
target/arm/translate-a64.c: In function ‘aarch64_tr_translate_insn’:
target/arm/translate-a64.c:2361:8: error: ‘post_index’ may be used
uninitialized in this function [-We
From: Alistair Francis
The EP108 was an early access development board that is no longer used.
Add an info message to convert any users to the ZCU102 instead. On QEMU
they are both identical.
This patch also updated the qemu-doc.texi file to indicate that the
EP108 has been deprecated.
Signed-o
From: Prasad J Pandit
An 'offset' parameter sent to highbank register r/w functions
could be greater than number(NUM_REGS=0x200) of hb registers,
leading to an OOB access issue. Add check to avoid it.
Reported-by: Moguofang (Dennis mo)
Signed-off-by: Prasad J Pandit
Message-id: 20171113062658.
On 13.11.2017 15:00, Markus Armbruster wrote:
> Thomas Huth writes:
>
>> The qdev_unplug() function contains a g_assert(hotplug_ctrl) statement,
>> so QEMU crashes when the user tries to device_add + device_del a device
>> that does not have a corresponding hotplug controller. This could be
>> pr
From: Alex Bennée
We are still seeing signals during translation time when we walk over
a page protection boundary. This expands the check to ensure the host
PC is inside the code generation buffer. The original suggestion was
to check versus tcg_ctx.code_gen_ptr but as we now segment the
transla
From: Alistair Francis
Allow the -smp command line option to control the number of CPUs we
create.
Signed-off-by: Alistair Francis
Reviewed-by: Eduardo Habkost
Reviewed-by: Emilio G. Cota
Tested-by: Emilio G. Cota
Message-id: 1510343626-25861-3-git-send-email-c...@braap.org
Signed-off-by: Pe
From: Subbaraya Sundeep
Voluntarily add myself as maintainer for Smartfusion2
Signed-off-by: Subbaraya Sundeep
Reviewed-by: Alistair Francis
Reviewed-by: Philippe Mathieu-Daudé
Message-id: 1510552520-3566-1-git-send-email-sundeep.l...@gmail.com
Signed-off-by: Peter Maydell
---
MAINTAINERS |
On Fri, Nov 10, 2017 at 03:19:34PM +, Stefan Hajnoczi wrote:
> I/O requests hang after stop/cont commands at least since QEMU 2.10.0
> with -drive iops=100:
>
> (guest)$ dd if=/dev/zero of=/dev/vdb oflag=direct count=1000
> (qemu) stop
> (qemu) cont
> ...I/O is stuck...
>
> This happe
e/pmaydell/qemu-arm.git
tags/pull-target-arm-20171113
for you to fetch changes up to d25f2a72272b9ffe0d06710d6217d1169bc2cc7d:
accel/tcg/translate-all: expand cpu_restore_state addr check (2017-11-13
13:55:27 +)
target
On 11/10/2017 10:51 AM, Vladimir Sementsov-Ogievskiy wrote:
> 10.11.2017 19:06, Eric Blake wrote:
>> On 11/09/2017 06:42 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi!
>>>
>>> Interesting fact: list/set_meta_context options are per-export,
>>> so, in the server we should keep context selection per
From: "Emilio G. Cota"
55c3cee ("qom: Introduce CPUClass.tcg_initialize", 2017-10-24)
introduces a per-CPUClass bool that we check so that the target CPU
is initialized for TCG only once. This works well except when
we end up creating more than one CPUClass, in which case we end
up incorrectly in
Thanks for the clarification.
But how does the target get the actual syscall return code, if
do_syscall() is supposed to return negative-target-errno?
I mean, in general the target code will check if the syscall returned -1, and
only then query errno?
But if QEMU's do_syscall returns -errno, and
Ladi Prosek writes:
> As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
> QEMU crashes with:
>
> kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
>
> if the ivshmem device is configured with more vectors than what the server
> supports. This is caused by the ivs
On 11/10/2017 06:12 PM, Paolo Bonzini wrote:
On 10/11/2017 21:25, Mike Nawrocki wrote:
This patch set does a few things. First, it switches the AMD CFI flash MMIO
operations from the old MMIO API to the new one. Second, it enables 8-byte wide
flash arrays. Finally, it adds flash interleaving usi
Would you accept a patch that allows the user to change the mouse ungrab key(s)
in QEMU?
It would look something like this:
-ungrab
or
-ungrab ,,...
If the user wanted the F19 key to be the ungrab key, this is what would be sent
to QEMU:
-ungrab F19
If the user wanted F16 and F17 held
On Fri 10 Nov 2017 04:19:34 PM CET, Stefan Hajnoczi wrote:
> I/O requests hang after stop/cont commands at least since QEMU 2.10.0
> with -drive iops=100:
>
> (guest)$ dd if=/dev/zero of=/dev/vdb oflag=direct count=1000
> (qemu) stop
> (qemu) cont
> ...I/O is stuck...
>
> This happens becau
On Fri, Nov 10, 2017 at 06:25:45PM +0100, Max Reitz wrote:
> On one hand, it is a good idea for bdrv_next() to return a strong
> reference because ideally nearly every pointer should be refcounted.
> This fixes intermittent failure of iotest 194.
>
> On the other, it is absolutely necessary for bd
1 - 100 of 306 matches
Mail list logo