John Snow writes:
> On 8/3/20 1:25 PM, Eric Blake wrote:
>> On 8/3/20 11:49 AM, John Snow wrote:
>>> UNION is split into two primary forms:
>>>
>>> 1. Simple (No discriminator nor base)
>>> 2. Flat (Discriminator and base)
>>>
>>> In expr.py, I notice that we modify the perceived type of the
>>>
aio_notify() does not set ctx->notified when called with
ctx->aio_notify_me disabled. In order to poll ctx->notified it is
therefore necessary to enable ctx->aio_notify_me.
This is suboptimal since expensive event_notifier_set(>notifier)
and event_notifier_test_and_clear(>notifier) calls required
Polling only monitors the ctx->notified field and does not need the
ctx->notifier EventNotifier to be signalled. Keep ctx->aio_notify_me
disabled while polling to avoid unnecessary EventNotifier syscalls.
This optimization improves virtio-blk 4KB random read performance by
18%. The following
The event_notifier_*() prefix can be confused with the EventNotifier
APIs that are also called event_notifier_*().
Rename the functions to aio_context_notifier_*() to make it clear that
they relate to the AioContext::notifier field.
Signed-off-by: Stefan Hajnoczi
---
util/async.c | 8
This patch series eliminates ctx->notifier EventNotifier activity when
aio_poll() is in polling mode. There is no need to use the EventNotifier since
a polling handler can detect that aio_notify() has been called by monitoring a
field in memory instead.
Optimizing out the EventNotifier calls
On 8/3/20 6:28 AM, Peter Maydell wrote:
> In arm_tr_init_disas_context() we have a FIXME comment that suggests
> "cpu_M0 can probably be the same as cpu_V0". This isn't in fact
> possible: cpu_V0 is used as a temporary inside gen_iwmmxt_shift(),
> and that function is called in various places
On Fri, Jul 31, 2020 at 5:24 AM Richard Henderson <
richard.hender...@linaro.org> wrote:
> On 7/22/20 2:16 AM, frank.ch...@sifive.com wrote:
> > From: Frank Chang
> >
> > Sign-extend vsaddu.vi immediate value.
> >
> > Signed-off-by: Frank Chang
> > ---
> >
These instructions use zero as the discriminator, not SP.
Signed-off-by: Peter Collingbourne
---
v2:
- fixed commit message
target/arm/translate-a64.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/target/arm/translate-a64.c b/target/arm/translate-a64.c
index
The name disas_ldst_pac is misleading as it implies the existence
of authenticating store instructions, so rename it to avoid that
implication.
Signed-off-by: Peter Collingbourne
---
target/arm/translate-a64.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On Mon, Aug 3, 2020 at 3:27 PM Peter Collingbourne wrote:
>
> These instructions use zero as the discriminator, not SP.
Oh, there is no such thing as STRAA/STRAB. I must have been confused
by the name of the function, disas_ldst_pac. I will send a v2 with a
fixed commit message, and another
Hi Alex,
Thank you for the reply.
Please see my inline response below.
-Original Message-
From: Alex Bennée
Sent: Friday, July 31, 2020 8:45 AM
To: Pincus, Josh
Cc: linux-ker...@vger.kernel.org; zha...@linux.alibaba.com;
virtio-...@lists.oasis-open.org; qemu-devel@nongnu.org
These instructions use zero as the discriminator, not SP.
Signed-off-by: Peter Collingbourne
---
target/arm/translate-a64.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/target/arm/translate-a64.c b/target/arm/translate-a64.c
index 8c0764957c..c996ca1393 100644
---
Public bug reported:
The host mouse pointer disappears when it is over a console window.
I am emulating quite simple hardware: just text console and no mouse. I
don't expect the mouse to have any effect on the emulated computers, but
I need to know where the mouse pointer is. That is important
Your pipeline has failed.
Project: QEMU ( https://gitlab.com/qemu-project/qemu )
Branch: master ( https://gitlab.com/qemu-project/qemu/-/commits/master )
Commit: 5c1c3e4f (
https://gitlab.com/qemu-project/qemu/-/commit/5c1c3e4f02e458cf280c677c817ae4fd1ed9bf10
)
Commit Message: Merge
On 8/3/20 2:58 AM, Thomas Huth wrote:
test-image-locking.c uses the qemu_lock_fd_test() function which is
only available on Posix-like systems.
Signed-off-by: Thomas Huth
Reviewed-by: John Snow
---
tests/Makefile.include | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 7/24/20 4:43 AM, Philippe Mathieu-Daudé wrote:
cmos_get_fd_drive_type() is declared in "hw/block/fdc.h".
This currently works because "hw/i386/pc.h" happens to
include it. Simplify including the correct header.
Fixes: 2055dbc1c9 ("acpi: move aml builder code for floppy device")
tes/ericb/tags/pull-bitmaps-2020-08-03'
> into staging (2020-08-03 15:13:49 +0100)
>
> are available in the Git repository at:
>
> https://git.linaro.org/people/pmaydell/qemu-arm.git
> tags/pull-target-arm-20200803
>
> for you to fetch changes up to 13557fd392890cbd985bc
On Mon, Aug 3, 2020 at 3:23 PM Daniel P. Berrangé wrote:
>
> On Mon, Aug 03, 2020 at 02:16:19PM +0200, Paolo Bonzini wrote:
> > On 03/08/20 13:36, Daniel P. Berrangé wrote:
> > >>> Given that QEMU needs to pass
> > >>> uint64 values, JSON was simply the wrong choice of format for QMP.
> > >
> > >
When support for this feature went in, the update to the
documentation was forgotten.
Fixes: 067e8b0f45d6
Reported-by: Peter Maydell
Signed-off-by: Richard Henderson
---
docs/devel/decodetree.rst | 29 ++---
1 file changed, 18 insertions(+), 11 deletions(-)
diff --git
On 8/3/20 3:54 PM, Nir Soffer wrote:
On Mon, Aug 3, 2020 at 9:19 PM John Snow wrote:
On 8/3/20 2:16 PM, Paolo Bonzini wrote:
On 03/08/20 20:10, John Snow wrote:
Heresy:
Docstrings could become part of the data format so they can be parsed,
analyzed and validated. Parsers largely treat
On 03.08.20 21:10, Alexander Bulekov wrote:
> On 200803 1432, Alexander Bulekov wrote:
>> On 200803 1336, Alexander Bulekov wrote:
>>> Hi,
>>> I applied this patch, but I can still trigger a segfault and heap
>>> overread through artist_reg_write -> fill_window. I dont know if these
>>> problems
Hi Philippe,
On Mon, Aug 3, 2020 at 12:08 PM Philippe Mathieu-Daudé wrote:
>
> Hi Havard,
>
> On 7/17/20 8:02 AM, Havard Skinnemoen wrote:
> > I also pushed this and the previous two patchsets to my qemu fork on github.
> > The branches are named npcm7xx-v[1-6].
> >
> >
Am 03.08.20 um 13:28 schrieb Stefan Weil:
> Am 03.08.20 um 12:51 schrieb Philippe Mathieu-Daudé:
>
>> Hi Sunil,
>>
>> On 8/1/20 1:31 AM, Sunil Muthuswamy wrote:
>>> The ask generally sounds reasonable. But, can you help me understand the
>>> full
>>> scope of the ask. Few questions:
>>> 1.
The GitHub action is restricted to https://github.com/qemu/qemu.
Signed-off-by: Stefan Weil
---
This patch adds a GitHub action for continuous integration builds
of QEMU for Windows.
The CI builds run on GitHub and include the WHPX code.
The action rules avoid unnecessary waste of resources by
This is my second attempt to contribute a patch which makes the -k switch
useful for sparc emulation as its value is used to emulate the dip switch
in a SUN keyboard for language layout setting.
Unfortunately my glib version is too old to compile later versions of qemu
so even though this patch
On Mon, Aug 3, 2020 at 9:19 PM John Snow wrote:
>
> On 8/3/20 2:16 PM, Paolo Bonzini wrote:
> > On 03/08/20 20:10, John Snow wrote:
> >> Heresy:
> >>
> >> Docstrings could become part of the data format so they can be parsed,
> >> analyzed and validated. Parsers largely treat comments like
The nrf51 SoC model wasn't setting the system_clock_scale
global.which meant that if guest code used the systick timer in "use
the processor clock" mode it would hang because time never advances.
Set the global to match the documented CPU clock speed for this SoC.
This SoC in fact doesn't have a
From: Kaige Li
GCC version 4.9.4 isn't clever enough to figure out that all
execution paths in disas_ldst() that use 'fn' will have initialized
it first, and so it warns:
/home/LiKaige/qemu/target/arm/translate-a64.c: In function ‘disas_ldst’:
From: Richard Henderson
The definition of top_bit used in this function is one higher
than that used in the Arm ARM psuedo-code, which put the error
indication at top_bit - 1 at the wrong place, which meant that
it wasn't visible to Auth.
Fixing the definition of top_bit requires more changes,
The imx_epit device has a software-controllable reset triggered by
setting the SWR bit in the CR register. An error in commit cc2722ec83ad9
means that we will end up assert()ing if the guest does this, because
the code in imx_epit_write() starts ptimer transactions, and then
imx_epit_reset() also
The NVIC provides an outbound qemu_irq "SYSRESETREQ" which it signals
when the guest sets the SYSRESETREQ bit in the AIRCR register. This
matches the hardware design (where the CPU has a signal of this name
and it is up to the SoC to connect that up to an actual reset
mechanism), but in QEMU it
Mostly devices don't need to care whether one of their output
qemu_irq lines is connected, because functions like qemu_set_irq()
silently do nothing if there is nothing on the other end. However
sometimes a device might want to implement default behaviour for the
case where the machine hasn't
The MSF2 SoC model and the Stellaris board code both wire
SYSRESETREQ up to a function that just invokes
qemu_system_reset_request(SHUTDOWN_CAUSE_GUEST_RESET);
This is now the default action that the NVIC does if the line is
not connected, so we can delete the handling code.
Signed-off-by:
)
are available in the Git repository at:
https://git.linaro.org/people/pmaydell/qemu-arm.git
tags/pull-target-arm-20200803
for you to fetch changes up to 13557fd392890cbd985bceba7f717e01efd674b8:
hw/timer/imx_epit: Avoid assertion when CR.SWR is written (2020-08-03
17:56:11 +0100
The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
global, which meant that if guest code used the systick timer in "use
the processor clock" mode it would hang because time never advances.
Set the global to match the documented CPU clock speed of these boards.
Judging by
Hello Yan,
I tryed the patches mentioned(the first one was already implemented in
the git master, the second wasn't). It did fix the IPv6 fragmentation
issue. So therefore, the focus needs to be on implementing proper layer
4 segmentation.
--Patrick
On Mon, 2020-08-03 at 09:37 +0300, Yan
On Mon, Aug 3, 2020 at 8:36 PM Henrik Carlqvist wrote:
>
> Thanks for finding my typos!
:-)
> On Mon, 3 Aug 2020 20:16:43 +0200
> Artyom Tarasenko wrote:
>
> > > > On Fri, 10 Jul 2020 20:19:11 +0200
> > > > Henrik Carlqvist wrote:
> > > >> hardcoded to allways use an US keyboard layout.
>
> >
libqemustub.a has been removed in commit ebedb37c8d ("Makefile: Remove
libqemustub.a"). Some remainders have been missed. Remove them now.
Signed-off-by: Thomas Huth
---
Makefile| 2 +-
scripts/coverity-scan/run-coverity-scan | 3 ---
tests/test-util-sockets.c
From: "Dr. David Alan Gilbert"
Map xattr names originating at the client; from get/set/remove xattr.
Signed-off-by: Dr. David Alan Gilbert
---
tools/virtiofsd/passthrough_ll.c | 101 ++-
1 file changed, 99 insertions(+), 2 deletions(-)
diff --git
From: "Dr. David Alan Gilbert"
Map xattr names coming from the host, i.e. listxattr.
Signed-off-by: Dr. David Alan Gilbert
---
tools/virtiofsd/passthrough_ll.c | 88
1 file changed, 88 insertions(+)
diff --git a/tools/virtiofsd/passthrough_ll.c
From: "Dr. David Alan Gilbert"
Hi,
This is a first cut of a xattr name mapping option for virtiofsd.
It allows the user of virtiofsd to define a fairly flexible mapping
from the view of the xattr names the host fs has and the ones that the
guest sees.
The hope is this allows things like:
From: "Dr. David Alan Gilbert"
Add an option to define mappings of xattr names so that
the client and host filesystems see different views.
This can be used to have different SELinux mappings as
seen by the guest, to run the virtiofsd with less privileges
(e.g. in a case where it can't set
On 200803 1432, Alexander Bulekov wrote:
> On 200803 1336, Alexander Bulekov wrote:
> > Hi,
> > I applied this patch, but I can still trigger a segfault and heap
> > overread through artist_reg_write -> fill_window. I dont know if these
> > problems are related to what this patch fixes. If not,
Hi Havard,
On 7/17/20 8:02 AM, Havard Skinnemoen wrote:
> I also pushed this and the previous two patchsets to my qemu fork on github.
> The branches are named npcm7xx-v[1-6].
>
> https://github.com/hskinnemoen/qemu
>
> This patch series models enough of the Nuvoton NPCM730 and NPCM750 SoCs
The code currently fails to compile on 32-bit big endian targets:
target/riscv/vector_helper.c: In function 'vext_clear':
target/riscv/vector_helper.c:154:16: error: cast to pointer from integer
of different size [-Werror=int-to-pointer-cast]
memset((void *)((uintptr_t)tail &
On 8/3/20 3:35 AM, Frank Chang wrote:
> i.e.
> /DEF_HELPER_6(vslide1up_vx_w, void, ptr, ptr, *tl*, ptr, env, i32)/ vs.
> /DEF_HELPER_6(vfslide1up_vf_h, void, ptr, ptr, *i64*, ptr, env, i32)/
>
> As /opfvf_trans()/ and /opivx_trans()/ are shared among other instructions,
> I wouldn't like to make
Thanks for finding my typos!
On Mon, 3 Aug 2020 20:16:43 +0200
Artyom Tarasenko wrote:
> > > On Fri, 10 Jul 2020 20:19:11 +0200
> > > Henrik Carlqvist wrote:
> > >> hardcoded to allways use an US keyboard layout.
> Can you please move this description to the commit message? (Fixing
> typo in
On 200803 1336, Alexander Bulekov wrote:
> Hi,
> I applied this patch, but I can still trigger a segfault and heap
> overread through artist_reg_write -> fill_window. I dont know if these
> problems are related to what this patch fixes. If not, let me know and
> I can create a separate launchpad
On Mon, 3 Aug 2020 at 17:53, Anthony PERARD wrote:
>
> xen patches
>
> bug fix
>
>
> Philippe Mathieu-Daudé (1):
> accel/xen: Fix xen_enabled() behavior on
On 8/3/20 2:16 PM, Paolo Bonzini wrote:
On 03/08/20 20:10, John Snow wrote:
Heresy:
Docstrings could become part of the data format so they can be parsed,
analyzed and validated. Parsers largely treat comments like non-semantic
information and discard it. Round-trip parsers that preserve
On Mon, Aug 3, 2020 at 7:52 PM Paolo Bonzini wrote:
>
> On 03/08/20 19:26, Henrik Carlqvist wrote:
> > Would you please consider my patch which implements the honor of the -k
> > switch
> > for sparc as a sun keyboard language dip switch setting instead of a hard
> > coded en-us keyboard layout?
On 03/08/20 20:10, John Snow wrote:
> Heresy:
>
> Docstrings could become part of the data format so they can be parsed,
> analyzed and validated. Parsers largely treat comments like non-semantic
> information and discard it. Round-trip parsers that preserve comments in
> any language are
On 8/3/20 8:01 AM, Paolo Bonzini wrote:
That said, after a bit more research I'm skeptical about the possibility
of using an off-the-shelf parser because most of them either don't
support comments, or are based on YAJL which simply discards comments.
Heresy:
Docstrings could become part of
On 03/08/2020 20.00, Philippe Mathieu-Daudé wrote:
> On 8/3/20 7:53 PM, Thomas Huth wrote:
>> On 30/06/2020 10.44, LIU Zhiwei wrote:
>>>
>>>
>>> On 2020/6/30 16:11, Thomas Huth wrote:
On 30/06/2020 08.56, LIU Zhiwei wrote:
>
>
> On 2020/6/29 6:51, Alistair Francis wrote:
>> On
Of course. I just tested the patch (used the branch from
https://github.com/patchew-project/qemu) and it didn't seem to help.
Could that be linked to the fact that the translation is only in the SMC
exception path? It should probably target the MSR exception path also
(and probably others too).
Maybe it's covered by EXCP_HYP_TRAP already...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1879587
Title:
Register number in ESR is incorrect for certain banked registers when
switching from
On 8/3/20 7:53 PM, Thomas Huth wrote:
> On 30/06/2020 10.44, LIU Zhiwei wrote:
>>
>>
>> On 2020/6/30 16:11, Thomas Huth wrote:
>>> On 30/06/2020 08.56, LIU Zhiwei wrote:
On 2020/6/29 6:51, Alistair Francis wrote:
> On Sun, Jun 28, 2020 at 7:30 AM Peter Maydell
> wrote:
On 30/06/2020 10.44, LIU Zhiwei wrote:
>
>
> On 2020/6/30 16:11, Thomas Huth wrote:
>> On 30/06/2020 08.56, LIU Zhiwei wrote:
>>>
>>>
>>> On 2020/6/29 6:51, Alistair Francis wrote:
On Sun, Jun 28, 2020 at 7:30 AM Peter Maydell
wrote:
> On Fri, 26 Jun 2020 at 22:53, Alistair
On 03/08/20 19:26, Henrik Carlqvist wrote:
> Would you please consider my patch which implements the honor of the -k switch
> for sparc as a sun keyboard language dip switch setting instead of a hard
> coded en-us keyboard layout?
>
> The initial patch mail was sent to the mailing list and the
On 8/3/20 1:25 PM, Eric Blake wrote:
On 8/3/20 11:49 AM, John Snow wrote:
UNION is split into two primary forms:
1. Simple (No discriminator nor base)
2. Flat (Discriminator and base)
In expr.py, I notice that we modify the perceived type of the 'type'
expression based on the two union
Hi,
I applied this patch, but I can still trigger a segfault and heap
overread through artist_reg_write -> fill_window. I dont know if these
problems are related to what this patch fixes. If not, let me know and
I can create a separate launchpad report for these.
-Alex
(1) Segfault:
cat << EOF |
Would you please consider my patch which implements the honor of the -k switch
for sparc as a sun keyboard language dip switch setting instead of a hard
coded en-us keyboard layout?
The initial patch mail was sent to the mailing list and the listed maintainers
of escc.c and is also available at
On 8/3/20 11:49 AM, John Snow wrote:
UNION is split into two primary forms:
1. Simple (No discriminator nor base)
2. Flat (Discriminator and base)
In expr.py, I notice that we modify the perceived type of the 'type'
expression based on the two union forms.
1a. Simple unions allow Array[T]
On 03/08/20 18:03, Markus Armbruster wrote:
>> In general it seems like a good idea to use a standard file format and
>> not "a standard file format except for two characters". :) We also
>> wouldn't be having discussions on editors.
>
> No argument. But towards which standard file format
Hi Igor, Paolo.
On 3/23/20 12:04 PM, Marcelo Tosatti wrote:
> On Mon, Mar 23, 2020 at 09:05:06AM +0100, Paolo Bonzini wrote:
>> On 22/03/20 17:27, Philippe Mathieu-Daudé wrote:
>
That 'ugly' is typically used within QEMU to deal with such things
probably due to its low complexity.
On Mon, Aug 3, 2020 at 4:27 AM Alex Bennée wrote:
>
>
> Lirong Yuan writes:
>
> > This allows gdb to access the target’s auxiliary vector,
> > which can be helpful for telling system libraries important details
> > about the hardware, operating system, and process.
> >
> > Signed-off-by: Lirong
Thanks for the bug report; I think this patch should fix it:
https://patchew.org/QEMU/20200803165409.15099-1-peter.mayd...@linaro.org/
Any chance you could test it?
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
On 7/30/20 1:34 PM, Igor Mammedov wrote:
> On Fri, 24 Jul 2020 18:52:59 +0200
> Philippe Mathieu-Daudé wrote:
>
>> No MIPS machine uses the ACPI cpu-hotplug feature
>> (QEMU implementation is X86 specific).
>
> if I recall correctly we were building it to satisfy symbol dependencies
> due to
When a coprocessor instruction in an AArch32 guest traps to AArch32
Hyp mode, the syndrome register (HSR) includes Rt and Rt2 fields
which are simply copies of the Rt and Rt2 fields from the trapped
instruction. However, if the instruction is trapped from AArch32 to
an AArch64 higher exception
From: Philippe Mathieu-Daudé
CONFIG_XEN is generated by configure and stored in "config-target.h",
which is (obviously) only include for target-specific objects.
This is a problem for target-agnostic objects as CONFIG_XEN is never
defined and xen_enabled() is always inlined as 'false'.
Fix by
-dm.git
tags/pull-xen-20200803
for you to fetch changes up to b3fcc98f391e9a60a369d825333b852871cf67b0:
accel/xen: Fix xen_enabled() behavior on target-agnostic objects (2020-08-03
17:39:38 +0100)
xen patches
bug fix
UNION is split into two primary forms:
1. Simple (No discriminator nor base)
2. Flat (Discriminator and base)
In expr.py, I notice that we modify the perceived type of the 'type'
expression based on the two union forms.
1a. Simple unions allow Array[T]
1b. Flat unions disallow Array[T]
From
From: "Edgar E. Iglesias"
Document the Xilinx Versal Virt board.
Signed-off-by: Edgar E. Iglesias
---
docs/system/arm/xlnx-versal-virt.rst | 176 +++
docs/system/target-arm.rst | 1 +
MAINTAINERS | 3 +-
3 files changed, 179
From: "Edgar E. Iglesias"
Hi,
This adds some basic documentation for the Xilinx Versal Virt board,
including a few command-line examples on how to run ARM Trusterd Firmware,
U-boot, Xen and Linux.
If this looks OK I'll send similar basic documentation for the ZynqMP and
Zynq.
Best regards,
On Mon, 3 Aug 2020 at 17:35, Anthony PERARD wrote:
>
> On Tue, Jul 28, 2020 at 12:09:25PM +0200, Philippe Mathieu-Daudé wrote:
> > CONFIG_XEN is generated by configure and stored in "config-target.h",
> > which is (obviously) only include for target-specific objects.
> > This is a problem for
Am 03.08.2020 um 18:03 hat Markus Armbruster geschrieben:
> Paolo Bonzini writes:
> > This means the two parts might be considered separately:
> >
> > - replacing single-quote with double-quote strings
> >
> > - replacing # comments with //
>
> If all we want is decent editor support out of the
On Tue, Jul 28, 2020 at 12:09:25PM +0200, Philippe Mathieu-Daudé wrote:
> CONFIG_XEN is generated by configure and stored in "config-target.h",
> which is (obviously) only include for target-specific objects.
> This is a problem for target-agnostic objects as CONFIG_XEN is never
> defined and
Alex Bennée writes:
> Pincus, Josh writes:
>
>> Hi,
>>
>>
>>
>> We were looking into a similar enhancement for the Virt I/O MMIO transport
>> and came across this project.
>>
>> This enhancement would be perfect for us.
>
> So there is certainly an interest in optimising MMIO based virtio
On Fri, 2020-07-03 at 15:24 +0800, Jason Wang wrote:
> On 2020/7/2 下午11:45, Peter Xu wrote:
> > On Thu, Jul 02, 2020 at 11:01:54AM +0800, Jason Wang wrote:
> > > So I think we agree that a new notifier is needed?
> > Good to me, or a new flag should be easier (IOMMU_NOTIFIER_DEV_IOTLB)?
>
> That
Paolo Bonzini writes:
> On 03/08/20 13:28, Markus Armbruster wrote:
We could remove them from the QAPI schema language. Flag day, and
git-blame becomes pretty much useless for a couple of years.
>>> Is that a nack or a "whatever"?
>> It's "is this really worth the trouble?" I guess
On Mon, 3 Aug 2020 at 15:13, Eric Blake wrote:
>
> The following changes since commit 6c5dfc9ccb643a0d50fdec9f10806b14960571d1:
>
> Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2020-08-03'
> into staging (2020-08-03 12:21:57 +0100)
>
> are available in the Git repository at:
>
>
On 8/1/20 6:13 AM, Helge Deller wrote:
> From: Sven Schnelle
>
> Signed-off-by: Sven Schnelle
> Signed-off-by: Helge Deller
> ---
> hw/display/artist.c | 24 +++-
> 1 file changed, 11 insertions(+), 13 deletions(-)
Looks ok, if not ideal.
Reviewed-by: Richard Henderson
Daniel P. Berrangé writes:
> On Mon, Aug 03, 2020 at 02:16:19PM +0200, Paolo Bonzini wrote:
>> On 03/08/20 13:36, Daniel P. Berrangé wrote:
>> >>> Given that QEMU needs to pass
>> >>> uint64 values, JSON was simply the wrong choice of format for QMP.
>> >
>> > I wasn't refering to RFC7159. The
Cc'ing Dmitry as he doesn't have lauchpad account :/
On 8/3/20 4:37 PM, Alexander Bulekov wrote:
> Public bug reported:
>
> Hello,
> Reproducer:
>
> cat << EOF | ./i386-softmmu/qemu-system-i386 \
> -device vmxnet3 -m 64 -nodefaults -qtest stdio -nographic
> outl 0xcf8 0x80001014
> outl 0xcfc
On 7/27/20 9:34 PM, Peter Maydell wrote:
> The nrf51 SoC model wasn't setting the system_clock_scale
> global.which meant that if guest code used the systick timer in "use
> the processor clock" mode it would hang because time never advances.
>
> Set the global to match the documented CPU clock
On Wed, Jul 29, 2020 at 04:40:54PM +0200, Andrew Jones wrote:
> > > +static inline void kvm_arm_steal_time_finalize(ARMCPU *cpu, Error
> > > **errp) {}
> >
> > Does this stub need to report an error to the caller via errp,
> > or is it a "never called but needs to exist to avoid linker errors" ?
On Sat, Aug 01, 2020 at 02:00:34PM +0200, Andrew Jones wrote:
> > > if (kvm_enabled()) {
> > > +hwaddr pvtime_base = vms->memmap[VIRT_PVTIME].base;
> > > +hwaddr pvtime_size = vms->memmap[VIRT_PVTIME].size;
> > > +
> > > +if (steal_time) {
> > > +
On 7/27/20 5:45 PM, Peter Maydell wrote:
> The imx_epit device has a software-controllable reset triggered by
> setting the SWR bit in the CR register. An error in commit cc2722ec83ad9
> means that we will end up assert()ing if the guest does this, because
> the code in imx_epit_write() starts
Public bug reported:
Hello,
Reproducer:
cat << EOF | ./i386-softmmu/qemu-system-i386 \
-device vmxnet3 -m 64 -nodefaults -qtest stdio -nographic
outl 0xcf8 0x80001014
outl 0xcfc 0xe0001000
outl 0xcf8 0x80001018
outl 0xcf8 0x80001004
outw 0xcfc 0x7
write 0x0 0x1 0xe1
write 0x1 0x1 0xfe
write 0x2
Public bug reported:
Hello,
Reproducer:
cat << EOF | ./i386-softmmu/qemu-system-i386 \
-device vmxnet3 -m 64 -nodefaults -qtest stdio -nographic
outl 0xcf8 0x80001010
outl 0xcfc 0xe000
outl 0xcf8 0x80001014
outl 0xcfc 0xe0001000
outl 0xcf8 0x80001018
outl 0xcf8 0x80001001
outl 0xcfc
Public bug reported:
Hello,
Reproducer:
cat << EOF | ./i386-softmmu/qemu-system-i386 \
-device vmxnet3 -m 64 -nodefaults -qtest stdio -nographic
outl 0xcf8 0x80001014
outl 0xcfc 0xe0001000
outl 0xcf8 0x80001018
outl 0xcf8 0x80001004
outw 0xcfc 0x7
outl 0xcf8 0x80001083
write 0x0 0x1 0xe1
write
Public bug reported:
Hello,
Reproducer:
cat << EOF | ./i386-softmmu/qemu-system-i386 \
-device vmxnet3 -m 64 -nodefaults -qtest stdio -nographic
outl 0xcf8 0x80001014
outl 0xcfc 0xe0001000
outl 0xcf8 0x80001018
outl 0xcf8 0x80001004
outw 0xcfc 0x7
write 0x0 0x1 0xe1
write 0x1 0x1 0xfe
write 0x2
Your pipeline has failed.
Project: QEMU ( https://gitlab.com/qemu-project/qemu )
Branch: master ( https://gitlab.com/qemu-project/qemu/-/commits/master )
Commit: 6c5dfc9c (
https://gitlab.com/qemu-project/qemu/-/commit/6c5dfc9ccb643a0d50fdec9f10806b14960571d1
)
Commit Message: Merge
Le 02/08/2020 à 15:39, cheng...@emindsoft.com.cn a écrit :
> From: Chen Gang
>
> Another DRM_IOCTL_I915 patches will be sent next.
>
> Signed-off-by: Chen Gang
> ---
> linux-user/ioctls.h| 3 +++
> linux-user/syscall.c | 35 +++
>
Public bug reported:
Hello,
This reproducer causes vmxnet3 to malloc 0xff030 bytes
cat << EOF | ./i386-softmmu/qemu-system-i386 \
-device vmxnet3 -m 64 -nodefaults -qtest stdio -nographic
outl 0xcf8 0x80001014
outl 0xcfc 0xe0001000
outl 0xcf8 0x80001018
outl 0xcf8 0x80001004
outw 0xcfc 0x7
On Sun, Aug 02, 2020 at 01:13 AM -0400, "Michael S. Tsirkin"
wrote:
> On Thu, Jul 30, 2020 at 04:07:31PM +0200, Marc Hartmayer wrote:
>> Since virtio existed even before it got standardized, the virtio
>> standard defines the following types of virtio devices:
>>
>> + legacy device (pre-virtio
From: Max Reitz
During migration, we release all bitmaps after storing them on disk, as
long as they are (1) stored on disk, (2) not read-only, and (3)
consistent.
(2) seems arbitrary, though. The reason we do not release them is
because we do not write them, as there is no need to; and then
Le 03/08/2020 à 11:46, Filip Bozuta a écrit :
> This patch implements functionality of following ioctls:
>
> BTRFS_IOC_INO_LOOKUP - Reading tree root id and path
>
> Read tree root id and path for a given file or directory.
> The name and tree root id are returned in an ioctl's third
>
The following changes since commit 6c5dfc9ccb643a0d50fdec9f10806b14960571d1:
Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2020-08-03' into
staging (2020-08-03 12:21:57 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git
From: Max Reitz
Test migrating from a VM with a persistent bitmap in the backing chain,
and then continuing that VM after the migration
Signed-off-by: Max Reitz
Message-Id: <20200730120234.49288-3-mre...@redhat.com>
Reviewed-by: Eric Blake
Signed-off-by: Eric Blake
---
1 - 100 of 218 matches
Mail list logo
