On 2019-01-21 at 02:21:39 -0500, Pankaj Gupta wrote:
>
> > > > ---
> > > > docs/nvdimm.txt | 21 -
> > > > qemu-options.hx | 4
> > > > 2 files changed, 24 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt
> > > > index 5f158a6.
Patchew URL: https://patchew.org/QEMU/20190116010106.27626-1-js...@redhat.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/
On 21/01/2019 02:31, no-re...@patchew.org wrote:
Patchew URL:
https://patchew.org/QEMU/1547554687-12687-1-git-send-email-liam.merw...@oracle.com/
...>
CC dma-helpers.o
CC vl.o
/tmp/qemu-test/src/block/sheepdog.c: In function 'find_vdi_name':
/tmp/qemu-test/src/block/sheepdog.c:
Patchew URL:
https://patchew.org/QEMU/20190115165710.20116-1-mhi...@scalecomputing.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20190115165710.20116-1-mhi...@scalecomputing.com
Type: series
Subject: [Qemu-devel] [PATCH v2] Q
On Thu, Jan 17, 2019 at 08:49:04PM +0800, Li Zhijian wrote:
> Since linux commit: cf8fa920cb42 ("i386: handle an initrd in highmem (version
> 2)")
> linux has supported initrd up to 4 GB, but the header field
> ramdisk_max is still set to 2 GB to avoid "possible bootloader bugs".
>
> When use '-k
On 1/19/19 10:29 PM, Richard Henderson wrote:
On 1/19/19 12:14 AM, Bastian Koppelmann wrote:
Acked-by: Alistair Francis
Reviewed-by: Richard Henderson
Signed-off-by: Bastian Koppelmann
Signed-off-by: Peer Adelt
---
target/riscv/insn32.decode | 2 ++
target/riscv/insn_trans
On 1/19/19 10:51 PM, Richard Henderson wrote:
On 1/19/19 12:14 AM, Bastian Koppelmann wrote:
+static bool trans_fsgnjn_s(DisasContext *ctx, arg_fsgnjn_s *a)
+{
+REQUIRE_FPU;
+if (a->rs1 == a->rs2) { /* FNEG */
+tcg_gen_xori_i64(cpu_fpr[a->rd], cpu_fpr[a->rs1], INT32_MIN);
+
On 1/20/19 2:24 AM, Richard Henderson wrote:
On 1/19/19 12:14 AM, Bastian Koppelmann wrote:
static bool trans_slli(DisasContext *ctx, arg_slli *a)
{
-gen_arith_imm(ctx, OPC_RISC_SLLI, a->rd, a->rs1, a->shamt);
+if (a->rd != 0) {
+TCGv t = tcg_temp_new();
+gen_get_gp
On 1/20/19 2:43 AM, Richard Henderson wrote:
On 1/19/19 12:14 AM, Bastian Koppelmann wrote:
Signed-off-by: Bastian Koppelmann
Signed-off-by: Peer Adelt
---
v3 -> v4:
- refactor tcg_gen_set_cond_tl(TCG_COND_LT,..) into gen_slt function
and reuse gen_arith(..., &gen_slt) for all tr
Patchew URL: https://patchew.org/QEMU/20190116041916.130523-1-...@ozlabs.ru/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bi
On 2019-01-18 15:47, ema...@freebsd.org wrote:
> From: Ed Maste
>
> Signed-off-by: Ed Maste
> ---
> Changes since v2:
> * remove fontconfig and freetype2, noted by Thomas Huth
>
> After this patch is applied someone with appropriate permissions will
> need to add the Cirrus-CI application in
Patchew URL: https://patchew.org/QEMU/20190116030815.27273-1-pet...@redhat.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!
On 1/15/2019 2:35 AM, Eduardo Habkost wrote:
Sorry, we do have a problem here:
On Thu, Dec 27, 2018 at 10:43:04AM +0800, Tao Xu wrote:
[...]
#define PC_COMPAT_3_0 \
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 09706ad51a..5296c73cd5 100644
--- a/target/i386/cpu.c
+++ b/target/i386
Ping
I believe all the discussion that happened in v2 applies here as well. Do we
have a plan for this series? Should I add something else (warning message
or doc note) to indicate a deprecation of the old meaning of the arguments?
Thanks,
DHB
On 11/7/18 11:09 AM, Daniel Henrique Barboza wro
On Mon, Jan 21, 2019 at 12:32:07AM -0800, no-re...@patchew.org wrote:
> Patchew URL:
> https://patchew.org/QEMU/20190116030815.27273-1-pet...@redhat.com/
>
>
>
> Hi,
>
> This series failed the docker-mingw@fedora build test. Please find the
> testing commands and
> their output below. If you
Thank you, I contacted IPXE folks.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1801073
Title:
util/zbin.c:390:37: error: absolute value function 'abs' given an
argument of type 'long int' but h
On Tue, 8 Jan 2019 at 22:31, Richard Henderson
wrote:
>
> Add storage space for the 5 encryption keys.
>
> Reviewed-by: Peter Maydell
> Signed-off-by: Richard Henderson
>
> v2: Remove pointless double migration.
> Use a struct to make it clear which half is which.
> ---
> target/arm/cp
On Fri, Jan 18, 2019 at 03:06:43PM +, Peter Maydell wrote:
> Here's my stab at a schedule for the 4.0 release:
>
> 2019-03-12: soft freeze
> 2019-03-19: hard freeze, tag rc0
> 2019-03-26: tag rc1
> 2019-04-02: tag rc2
> 2019-04-09: tag rc3
> 2019-04-16: release, or rc4 if needed
> 2019-04-23:
On Fri, Jan 18, 2019 at 01:01:38PM +0100, Stefano Garzarella wrote:
> This patch series is based on "[PATCH v3 0/4] QEMU changes to do PVH boot" and
> provides a PVH option rom that can be used with SeaBIOS to boot uncompressed
> kernel using the x86/HVM direct boot ABI.
>
> Patches 1 and 2 are to
On 2019-01-21 10:13, Thomas Huth wrote:
> On 2019-01-18 15:47, ema...@freebsd.org wrote:
>> From: Ed Maste
>>
>> Signed-off-by: Ed Maste
>> ---
>> Changes since v2:
>> * remove fontconfig and freetype2, noted by Thomas Huth
>>
>> After this patch is applied someone with appropriate permissions
Cc'ing Corey, the tests author.
On 1/18/19 7:54 PM, Peter Maydell wrote:
> The ipmi-bt-test fails intermittently, especially on the NetBSD VM.
> The frequency of this failure has recently gone up sharply to the
> point that I'm having to retry the NetBSD build multiple times
> to get a pass when m
On Mon, Jan 21, 2019 at 11:39 AM Philippe Mathieu-Daudé
wrote:
>
> Cc'ing Corey, the tests author.
>
> On 1/18/19 7:54 PM, Peter Maydell wrote:
> > The ipmi-bt-test fails intermittently, especially on the NetBSD VM.
> > The frequency of this failure has recently gone up sharply to the
> > point th
On 18.01.19 15:37, Igor Mammedov wrote:
> On Fri, 18 Jan 2019 13:53:14 +0100
> David Hildenbrand wrote:
>
>> On 18.01.19 11:20, Igor Mammedov wrote:
>>> On Wed, 16 Jan 2019 12:35:22 +0100
>>> David Hildenbrand wrote:
>>>
Override the PCI device hotplug handler to properly handle the
On 18/01/19 20:28, Michael S. Tsirkin wrote:
> OK, and I also think we should rename it PCIE -> PCI_EXPRESS_, this way
> everything PCI starts with PCI.
I have no preference for PCIE vs. PCI_EXPRESS (PCIE is universally known
and shorter, but it's okay either way), but I agree it makes sense to
re
On Sun, Jan 20, 2019 at 05:51:06PM -0800, no-re...@patchew.org wrote:
> Patchew URL:
> https://patchew.org/QEMU/20190115111007.27159-1-stefa...@redhat.com/
...
> /tmp/qemu-test/src/block/sheepdog.c: In function 'find_vdi_name':
> /tmp/qemu-test/src/block/sheepdog.c:1239:5: error: 'strncpy' specifi
18' into
staging (2019-01-18 16:56:15 +)
are available in the Git repository at:
https://git.linaro.org/people/pmaydell/qemu-arm.git
tags/pull-target-arm-20190121
for you to fetch changes up to 0d4bfd7df809863b1f45fad35229fb9419527d06:
target/arm: Implement PMSWINC (2019-01-21 1
On 1/18/19 7:36 PM, Peter Maydell wrote:
> In virtio_balloon_get_config() we initialize a struct virtio_balloon_config
> which we then copy to guest memory. However, the local variable is not
> zero initialized. This works OK at the moment because we initialize
> all the fields in it; however an up
Patchew URL: https://patchew.org/QEMU/20190116101049.8929-1-kra...@redhat.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/
On Fri, Jan 18, 2019 at 05:31:01PM +, Daniel P. Berrangé wrote:
> When generating the trace-events-all file, the build system simply
> concatenates all the individual trace-events files. If any one of those
> files does not have a final newline, the printf format string will have
> the contents
On Fri, Jan 18, 2019 at 05:31:00PM +, Daniel P. Berrangé wrote:
> diff --git a/hw/display/qxl.c b/hw/display/qxl.c
> index 8e9a65e75b..eefdf4baac 100644
> --- a/hw/display/qxl.c
> +++ b/hw/display/qxl.c
> @@ -1763,7 +1763,8 @@ async_common:
> qxl_set_mode(d, val, 0);
> break;
Aleksandar Markovic writes:
> From: Aleksandar Markovic
>
> Add Citrix, Huawei, Intel, and Microsoft to domain map, and
> update Wave Computuing group.
>
> Aleksandar Markovic (2):
> contrib: gitdm: Update domain-map
> contrib: gitdm: Update Wave Computing group
>
> contrib/gitdm/domain-m
On Fri, Jan 18, 2019 at 12:14:14PM -0600, Eric Blake wrote:
> On 1/18/19 11:31 AM, Daniel P. Berrangé wrote:
> > +def c_macro_to_format(macro):
> > +if macro.startswith("PRI"):
> > +return macro[3]
> > +
> > +if macro == "TARGET_FMT_plx":
> > +return "%016x"
>
> Do we reall
On Mon, Jan 21, 2019 at 08:19:03AM +, Liam Merwick wrote:
> On 21/01/2019 02:31, no-re...@patchew.org wrote:
> > Patchew URL:
> > https://patchew.org/QEMU/1547554687-12687-1-git-send-email-liam.merw...@oracle.com/
> ...>
> >CC dma-helpers.o
> >CC vl.o
> > /tmp/qemu-test/src/b
Patchew URL: https://patchew.org/QEMU/20190115143650.15725-1-jus...@mail.ru/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bi
ema...@freebsd.org writes:
> From: Ed Maste
>
> Signed-off-by: Ed Maste
> ---
> Changes since v2:
> * remove fontconfig and freetype2, noted by Thomas Huth
>
> After this patch is applied someone with appropriate permissions will
> need to add the Cirrus-CI application in GitHub.
I should b
[This is the Linux kernel part, git tree is available at
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git
vfio-ccw-eagain-caps
The companion QEMU patches are available at
https://github.com/cohuck/qemu vfio-ccw-caps]
Currently, vfio-ccw only relays START SUBCHANNEL requests t
Rework handling of multiple I/O requests to return -EAGAIN if
we are already processing an I/O request. Introduce a mutex
to disallow concurrent writes to the I/O region.
The expectation is that userspace simply retries the operation
if it gets -EAGAIN.
We currently don't allow multiple ssch requ
The vfio-ccw code will need this, and it matches treatment of ssch
and csch.
Reviewed-by: Pierre Morel
Signed-off-by: Cornelia Huck
---
drivers/s390/cio/ioasm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/s390/cio/ioasm.c b/drivers/s390/cio/ioasm.c
index 14d328338ce2..08eb10283b
To be replaced with a real linux-headers update.
Signed-off-by: Cornelia Huck
---
linux-headers/linux/vfio.h | 4
linux-headers/linux/vfio_ccw.h | 12
2 files changed, 16 insertions(+)
diff --git a/linux-headers/linux/vfio.h b/linux-headers/linux/vfio.h
index ceb6453394..
On Fri, Jan 18, 2019 at 06:54:02PM +, Peter Maydell wrote:
> The ipmi-bt-test fails intermittently, especially on the NetBSD VM.
> The frequency of this failure has recently gone up sharply to the
> point that I'm having to retry the NetBSD build multiple times
> to get a pass when merging pull
Allow to extend the regions used by vfio-ccw. The first user will be
handling of halt and clear subchannel.
Signed-off-by: Cornelia Huck
---
drivers/s390/cio/vfio_ccw_ops.c | 181
drivers/s390/cio/vfio_ccw_private.h | 38 ++
include/uapi/linux/vfio.h
Add a region to the vfio-ccw device that can be used to submit
asynchronous I/O instructions. ssch continues to be handled by the
existing I/O region; the new region handles hsch and csch.
Interrupt status continues to be reported through the same channels
as for ssch.
Signed-off-by: Cornelia Huc
When we get a solicited interrupt, the start function may have
been cleared by a csch, but we still have a channel program
structure allocated. Make it safe to call the cp accessors in
any case, so we can call them unconditionally.
Signed-off-by: Cornelia Huck
---
drivers/s390/cio/vfio_ccw_cp.c
[This is the QEMU part, git tree is available at
https://github.com/cohuck/qemu vfio-ccw-caps
The companion Linux kernel patches are available at
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git
vfio-ccw-eagain-caps]
Currently, vfio-ccw only relays START SUBCHANNEL requests t
A vfio-ccw device may provide an async command subregion for
issuing halt/clear subchannel requests. If it is present, use
it for sending halt/clear request to the device; if not, fall
back to emulation (as done today).
Signed-off-by: Cornelia Huck
---
hw/s390x/css.c | 27 +++--
Cc'ing Daniel & Alex.
On 1/18/19 11:33 PM, Laszlo Ersek wrote:
> The roms/edk2 submodule can help with three goals:
> - build the OVMF and ArmVirtQemu virtual UEFI firmware platforms (to be
> implemented later),
> - build the EfiRom tool on the fly, which is used in roms/Makefile, for
> buildi
Hi Laszlo,
On 1/18/19 11:33 PM, Laszlo Ersek wrote:
> Building the EfiRom utility from "roms/edk2/BaseTools" should make
> "roms/Makefile" more self-contained. Otherwise, we'd call the system-wide
> EfiRom for building the combined iPXE option ROMs, but call the sibling
> utilities from "roms/edk2
On Mon, Jan 21, 2019 at 11:25:57AM +0100, Paolo Bonzini wrote:
> On 18/01/19 20:28, Michael S. Tsirkin wrote:
> > OK, and I also think we should rename it PCIE -> PCI_EXPRESS_, this way
> > everything PCI starts with PCI.
>
> I have no preference for PCIE vs. PCI_EXPRESS (PCIE is universally known
On 1/21/19 12:27 PM, Philippe Mathieu-Daudé wrote:
> Hi Laszlo,
>
> On 1/18/19 11:33 PM, Laszlo Ersek wrote:
>> Building the EfiRom utility from "roms/edk2/BaseTools" should make
>> "roms/Makefile" more self-contained. Otherwise, we'd call the system-wide
>> EfiRom for building the combined iPXE o
Patchew URL: https://patchew.org/QEMU/20181214105642.673-1-cferg...@redhat.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!
Hi Eric,
As I informed you earlier, I am working on adding the hot-add support for
pc-dimm
and nvdimm on top of this series using the pl061 GPIO pins as a way to inject
memory hot add events to the Guest. I came across a problem while testing
my patches which looks like is related to the way SRAT
On 16.01.19 15:46, Eric Blake wrote:
> On 1/16/19 5:35 AM, David Hildenbrand wrote:
>> From: Pankaj Gupta
>>
>> This is the current protoype of virtio-pmem. Support will require
>> machine changes for the architectures that will support it, so it will
>> not yet be compiled.
>>
>> TODO:
>> - Use s
On 21/01/19 12:26, Yang Zhong wrote:
> On Mon, Jan 21, 2019 at 11:25:57AM +0100, Paolo Bonzini wrote:
>> On 18/01/19 20:28, Michael S. Tsirkin wrote:
>>> OK, and I also think we should rename it PCIE -> PCI_EXPRESS_, this way
>>> everything PCI starts with PCI.
>>
>> I have no preference for PCIE v
* David Hildenbrand (da...@redhat.com) wrote:
> On 16.01.19 15:46, Eric Blake wrote:
> > On 1/16/19 5:35 AM, David Hildenbrand wrote:
> >> From: Pankaj Gupta
> >>
> >> This is the current protoype of virtio-pmem. Support will require
> >> machine changes for the architectures that will support it,
On 2019-01-17 17:16, Julia Suvorova wrote:
> Run qtest with a socket that connects QEMU chardev and test code.
>
> Signed-off-by: Julia Suvorova
> ---
> tests/libqtest.c | 26 ++
> tests/libqtest.h | 11 +++
> 2 files changed, 37 insertions(+)
>
> diff --git a/te
On 2019-01-17 17:16, Julia Suvorova wrote:
> Using of global_qtest is not required here. Let's replace functions like
> readl() with the corresponding qtest_* counterparts.
>
> Signed-off-by: Julia Suvorova
> ---
> tests/microbit-test.c | 247 ++
> 1 file
Patchew URL:
https://patchew.org/QEMU/20190115184229.73688-1-ema...@freefall.freebsd.org/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT B
Hi Laszlo,
On 1/18/19 11:33 PM, Laszlo Ersek wrote:
> Introduce the following build scripts under "tests/uefi-test-tools":
>
> * "build.sh" builds a single module (a UEFI application) from
> UefiTestToolsPkg, for a single QEMU emulation target.
>
> "build.sh" relies on cross-compilers when t
On 1/21/19 8:54 AM, no-re...@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20190116010106.27626-1-js...@redhat.com/
>
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
> time make docker-test-mingw@fedora SHOW_ENV=1 J=14
> === TEST SCRIPT END ===
>
> CC crypto/block.o
> CC cryp
On Mon, Jan 21, 2019 at 01:21:34PM +0100, Philippe Mathieu-Daudé wrote:
> On 1/21/19 8:54 AM, no-re...@patchew.org wrote:
> > Patchew URL:
> > https://patchew.org/QEMU/20190116010106.27626-1-js...@redhat.com/
> >
> > === TEST SCRIPT BEGIN ===
> > #!/bin/bash
> > time make docker-test-mingw@fedora
Should be fixed here:
http://git.ipxe.org/ipxe.git/commitdiff/956f6a722
Btw. how do you pull changes from ipxe into qemu repo?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1801073
Title:
util/zbi
On 2019-01-17 17:16, Julia Suvorova via Qemu-devel wrote:
> Some functional tests for:
> Basic reception/transmittion
> Suspending
> INTEN* registers
>
> Signed-off-by: Julia Suvorova
> ---
> tests/microbit-test.c | 84 +++
> 1 file changed, 84
On Mon, 21 Jan 2019 at 12:47, Martin Liska wrote:
>
> Should be fixed here:
> http://git.ipxe.org/ipxe.git/commitdiff/956f6a722
>
> Btw. how do you pull changes from ipxe into qemu repo?
The next step is a QEMU patch which updates our git submodule
to point at a version of IPXE with the fix and a
On 15.01.19 12:10, Stefan Hajnoczi wrote:
> LUKS encryption reserves clusters for its own payload data. The size of
> this area must be included in the qemu-img measure calculation so that
> we arrive at the correct minimum required image size.
>
> (Ab)use the qcrypto_block_create() API to determ
On 15.01.19 12:10, Stefan Hajnoczi wrote:
> The previous patch includes the LUKS payload overhead into the qemu-img
> measure calculation for qcow2. Update qemu-iotests 178 to exercise this
> new code path.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> tests/qemu-iotests/178 | 8 +++
On 21.01.19 14:08, Max Reitz wrote:
> On 15.01.19 12:10, Stefan Hajnoczi wrote:
>> LUKS encryption reserves clusters for its own payload data. The size of
>> this area must be included in the qemu-img measure calculation so that
>> we arrive at the correct minimum required image size.
>>
>> (Ab)us
It only supported RXv1 instructions.
Signed-off-by: Yoshinori Sato
---
disas/Makefile.objs |1 +
disas/rx.c | 1277 +++
include/disas/bfd.h |5 +
3 files changed, 1283 insertions(+)
create mode 100644 disas/rx.c
diff --git a/disa
Hello.
This patch series is added Renesas RX target emulation.
My git repository is bellow.
git://git.pf.osdn.net/gitroot/y/ys/ysato/qemu.git
Since my understanding is not enough,
I want many comments to make this a good one.
Thanks.
Yoshinori Sato (11):
TCG translation
RX CPU definition
Signed-off-by: Yoshinori Sato
---
target/rx/helper.c | 143 +
1 file changed, 143 insertions(+)
create mode 100644 target/rx/helper.c
diff --git a/target/rx/helper.c b/target/rx/helper.c
new file mode 100644
index 00..1d00732c0c
--- /d
This module supported only non FIFO type.
Hardware manual.
https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01uh0033ej0140_rx62n.pdf?key=086621e01bd70347c18ea7f794aa9cc3
Signed-off-by: Yoshinori Sato
---
hw/char/Makefile.objs | 2 +-
hw/char/renesas_sci.c | 279
Signed-off-by: Yoshinori Sato
---
MAINTAINERS | 20
1 file changed, 20 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index af339b86db..c2aae46ffa 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -272,6 +272,14 @@ F: include/hw/riscv/
F: linux-user/host/riscv32/
F: linu
rx62n - RX62N cpu.
rxqemu - QEMU virtual target.
Signed-off-by: Yoshinori Sato
---
hw/rx/Makefile.objs | 1 +
hw/rx/rx62n.c | 233 ++
hw/rx/rxqemu.c| 106 +++
include/hw/rx/rx.h| 7 ++
include/hw/rx/rx
Signed-off-by: Yoshinori Sato
---
arch_init.c| 2 ++
configure | 8
default-configs/rx-softmmu.mak | 7 +++
include/sysemu/arch_init.h | 1 +
target/rx/Makefile.objs| 2 ++
5 files changed, 20 insertions(+)
create mode 100644 defa
Signed-off-by: Yoshinori Sato
---
target/rx/gdbstub.c | 114
target/rx/monitor.c | 38 ++
2 files changed, 152 insertions(+)
create mode 100644 target/rx/gdbstub.c
create mode 100644 target/rx/monitor.c
diff --git a/target/r
Signed-off-by: Yoshinori Sato
---
target/rx/cpu-qom.h | 54 +
target/rx/cpu.c | 226
target/rx/cpu.h | 212
3 files changed, 492 insertions(+)
create mode 100644 target/rx/c
This implementation supported only ICUa.
Hardware manual.
https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01uh0033ej0140_rx62n.pdf?key=086621e01bd70347c18ea7f794aa9cc3
Signed-off-by: Yoshinori Sato
---
hw/intc/Makefile.objs| 1 +
hw/intc/rx_icu.c | 313
This part only supported RXv1 instructions.
Instruction manual.
https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01us0032ej0120_rxsm.pdf
Signed-off-by: Yoshinori Sato
---
target/rx/helper.h| 22 +
target/rx/op_helper.c | 548 +
target/rx/translate.c | 3003
renesas_tmr: 8bit timer modules.
renesas_cmt: 16bit compare match timer modules.
This part use many renesas's CPU.
Hardware manual.
https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01uh0033ej0140_rx62n.pdf?key=086621e01bd70347c18ea7f794aa9cc3
Signed-off-by: Yoshinori Sato
---
hw/
On 17/01/19 13:49, Li Zhijian wrote:
> Long long ago, linux kernel has supported up to 4G initrd, but it's header
> still hard code to allow loading initrd below 2G only.
> cutting from arch/boot/x86/header.S:
> # (Header version 0x0203 or later) the highest safe address for the contents
> # of
These are the remaining two patches, rebased to current upstream.
Patch 1: Rework unplug handler (introduce unplug_request handler) which
also fixes some unplug scenarios
Patch 2: Handle leftover unplug requests on reset
v2 -> v3:
- Rebased
v1 -> v2:
- Some rewordings in patch descripti
When resetting the guest we should unplug and remove all devices that
are still pending. Otherwise the fresh guest will see devices that will
suddenly vanish.
Can be triggered e.g. via
(hmp) device_add virtio-mouse-pci,id=test
(hmp) stop
(hmp) device_del test
(hmp) system_reset
(hmp) c
The device
On 2019-01-21 14:15, Yoshinori Sato wrote:
> This part only supported RXv1 instructions.
> Instruction manual.
> https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01us0032ej0120_rxsm.pdf
>
> Signed-off-by: Yoshinori Sato
> ---
[...]
> diff --git a/target/rx/op_helper.c b/target/rx/
On 21.01.19 14:15, Max Reitz wrote:
> On 21.01.19 14:08, Max Reitz wrote:
>> On 15.01.19 12:10, Stefan Hajnoczi wrote:
>>> LUKS encryption reserves clusters for its own payload data. The size of
>>> this area must be included in the qemu-img measure calculation so that
>>> we arrive at the correct
PCI on s390x is really weird and how it was modeled in QEMU might not have
been the right choice. Anyhow, right now it is the case that:
- Hotplugging a PCI device will silently create a zPCI device
(if none is provided)
- Hotunplugging a zPCI device will unplug the PCI device (if any)
- Hotunplu
On 21.01.19 13:02, Dr. David Alan Gilbert wrote:
> * David Hildenbrand (da...@redhat.com) wrote:
>> On 16.01.19 15:46, Eric Blake wrote:
>>> On 1/16/19 5:35 AM, David Hildenbrand wrote:
From: Pankaj Gupta
This is the current protoype of virtio-pmem. Support will require
machine
On Mon, Jan 21, 2019 at 02:15:03PM +0100, Max Reitz wrote:
> On 21.01.19 14:08, Max Reitz wrote:
> > On 15.01.19 12:10, Stefan Hajnoczi wrote:
> >> LUKS encryption reserves clusters for its own payload data. The size of
> >> this area must be included in the qemu-img measure calculation so that
>
On Sat, 19 Jan 2019 at 14:00, Luc Michel wrote:
>
> a TID or PID value means "any thread" (resp. "any process"). This commit
> fixes the different combinations when at least one value is 0.
>
> When both are 0, the function now returns the first attached CPU,
> instead of the CPU with TID 1, which
875f8ec8:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190118' into
> staging (2019-01-18 16:56:15 +)
>
> are available in the Git repository at:
>
> https://git.linaro.org/people/pmaydell/qemu-arm.git
> tags/pull
On Mon, 21 Jan 2019 at 10:40, Philippe Mathieu-Daudé wrote:
>
> On Mon, Jan 21, 2019 at 11:39 AM Philippe Mathieu-Daudé
> wrote:
> >
> > Cc'ing Corey, the tests author.
> >
> > On 1/18/19 7:54 PM, Peter Maydell wrote:
> > > The ipmi-bt-test fails intermittently, especially on the NetBSD VM.
> > >
Hi Shameer,
On 1/21/19 12:44 PM, Shameerali Kolothum Thodi wrote:
> Hi Eric,
>
> As I informed you earlier, I am working on adding the hot-add support for
> pc-dimm
> and nvdimm on top of this series using the pl061 GPIO pins as a way to inject
> memory hot add events to the Guest. I came across
Hi,
Just want to clarify your suggestions.
1) migrate=off/share=on
I'm not sure that adding new flag 'migrate=off' is a good idea. I think that
share=on as you suggested at first is enough.
* It's a new flag which has sense only with share=on
* It seems to that the meaning of this flag isn't cle
When size and format of the display surface stays the same we can just
tag the guest display as dirty and be done with it.
There is no need need to resize the vnc server display or to touch the
vnc client dirty bits. On the next refresh cycle
vnc_refresh_server_surface() will check for actual dis
From: Daniel P. Berrangé
The icon associated with a GtkWindow is just a hint to window managers
and not all of them will honour it. Some will instead want to show the
icon listed by the .desktop file. The desktop file is located based on
the application ID, which is set using g_set_prgname. QEMU
From: Daniel P. Berrangé
Modern desktop environments can render icons at very large sizes,
especially with high DPI screens. Providing a 32x32 pixel bitmap is
nowhere near sufficient anymore.
When displayed in GNOME shell the QEMU icon looks awful, having been
scaled up to at least x4 its base s
The following changes since commit 681d61362d3f766a00806b89d6581869041f73cb:
Merge remote-tracking branch 'remotes/jnsnow/tags/bitmaps-pull-request' into
staging (2019-01-17 12:48:42 +)
are available in the git repository at:
git://git.kraxel.org/qemu tags/ui-20190121-pull-re
From: Daniel P. Berrangé
QEMU currently installs logos to $prefix/share/qemu/ which means no GUI
toolkit or applications can find them by default.
The accepted standards for desktop applications declare that application
logos / icons should be installed under $prefix/share/icons, so use this
dir
From: Alexander Kanavin
It was assumed that mesa provides the necessary X11 includes,
but it is not always the case, as it can be configured without x11 support.
Signed-off-by: Alexander Kanavin
Reviewed-by: Philippe Mathieu-Daudé
Message-id: 20190116113751.17177-1-alex.kana...@gmail.com
[ kr
On 1/21/19 12:19 AM, Thomas Huth wrote:
On 2019-01-18 19:54, Peter Maydell wrote:
The ipmi-bt-test fails intermittently, especially on the NetBSD VM.
The frequency of this failure has recently gone up sharply to the
point that I'm having to retry the NetBSD build multiple times
to get a pass whe
On Mon, Jan 21, 2019 at 12:57:16PM +, Peter Maydell wrote:
> On Mon, 21 Jan 2019 at 12:47, Martin Liska wrote:
> >
> > Should be fixed here:
> > http://git.ipxe.org/ipxe.git/commitdiff/956f6a722
> >
> > Btw. how do you pull changes from ipxe into qemu repo?
>
> The next step is a QEMU patch w
On Mon, 21 Jan 2019 at 14:32, Corey Minyard wrote:
>
> On 1/21/19 12:19 AM, Thomas Huth wrote:
> > On 2019-01-18 19:54, Peter Maydell wrote:
> >> The ipmi-bt-test fails intermittently, especially on the NetBSD VM.
> >> The frequency of this failure has recently gone up sharply to the
> >> point th
1 - 100 of 350 matches
Mail list logo
