On 12.07.19 09:35, Pankaj Gupta wrote:
> Remove transactional & non transactional device info
> for virtio pmem.
Can you explain and add *why* ?
>
> Signed-off-by: Pankaj Gupta
> ---
> hw/virtio/virtio-pmem-pci.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/hw/virtio/virtio-pmem
On 12.07.19 09:35, Pankaj Gupta wrote:
> Coverity reported memory region returns zero
> for non-null value. This is because of wrong
> arguments to '?:' , fixing this.
>
> Signed-off-by: Pankaj Gupta
> ---
> hw/virtio/virtio-pmem-pci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
On Fri, Jul 12, 2019 at 09:34:46AM -0500, Michael Roth wrote:
> Quoting David Gibson (2019-07-12 01:46:19)
> > On Thu, Jul 11, 2019 at 08:19:34PM -0500, Michael Roth wrote:
> > > This implements the H_TPM_COMM hypercall, which is used by an
> > > Ultravisor to pass TPM commands directly to the host
On Fri, Jul 12, 2019 at 10:13:48AM -0500, Michael Roth wrote:
> Quoting David Gibson (2019-07-12 01:40:27)
> > On Thu, Jul 11, 2019 at 08:19:33PM -0500, Michael Roth wrote:
> > > For now this only covers hcalls relating to TPM communication since
> > > it's the only one particularly important from
On Fri, Jul 05, 2019 at 07:01:38PM +0800, Liu Yi L wrote:
> This patch adds vfio implementation PCIPASIDOps.alloc_pasid/free_pasid().
> These two functions are used to propagate guest pasid allocation and
> free requests to host via vfio container ioctl.
As I said in an earlier comment, I think do
Doh! Forgot the v2 tag!
On Mon, 2019-07-15 at 16:19 +1000, Rashmica Gupta wrote:
> Rebased on Peter's target-arm.next branch.
>
> v2: Addressed Andrew's feedback, added debounce regs, renamed get/set
> to
> read/write to minimise confusion with a 'set' of registers.
>
> Rashmica Gupta (2):
> h
GPIO pins are arranged in groups of 8 pins labeled A,B,..,Y,Z,AA,AB,AC.
(Note that the ast2400 controller only goes up to group AB).
A set has four groups (except set AC which only has one) and is
referred to by the groups it is composed of (eg ABCD,EFGH,...,YZAAAB).
Each set is accessed and contro
Rebased on Peter's target-arm.next branch.
v2: Addressed Andrew's feedback, added debounce regs, renamed get/set to
read/write to minimise confusion with a 'set' of registers.
Rashmica Gupta (2):
hw/gpio: Add basic Aspeed GPIO model for AST2400 and AST2500
aspeed: add a GPIO controller to the
Signed-off-by: Rashmica Gupta
---
hw/arm/aspeed_soc.c | 17 +
include/hw/arm/aspeed_soc.h | 3 +++
2 files changed, 20 insertions(+)
diff --git a/hw/arm/aspeed_soc.c b/hw/arm/aspeed_soc.c
index c6fb3700f2..ff422c8ad1 100644
--- a/hw/arm/aspeed_soc.c
+++ b/hw/arm/aspeed_s
Recent commit 2f2c4e4731 "Convert "translator internals" docs to RST,
move to devel manual" and commit 282d36b5e2 "qemu-tech.texi: Remove
"QEMU compared to other emulators" section" removed @node, but left
their @menu entries behind. This broke building qemu-doc.info (but
not qemu-doc.{html,pdf,tx
The qemu-doc.{html,info,pdf,txt} depend on qemu-doc.texi and its
include files. Except qemu-tech.texi is missing. Has always been
missing as far as I can see. Fix it.
Signed-off-by: Markus Armbruster
---
Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Makefile b
*** BLURB HERE ***
Markus Armbruster (2):
Makefile: Fix missing dependency of on qemu-tech.texi
qemu-tech: Fix dangling @menu entries
Makefile | 3 ++-
qemu-tech.texi | 3 ---
2 files changed, 2 insertions(+), 4 deletions(-)
--
2.21.0
Mark Cave-Ayland writes:
> On 11/07/2019 15:45, Markus Armbruster wrote:
>
>> Mark Cave-Ayland writes:
>>
>>> Something also looks a bit odd with distclean here on a fresh checkout:
>>>
>>> build@ezio:~/src/qemu/git/tmp/qemu$ make distclean
>>> LD recurse-clean.mo
>>> cc: fatal error: no
Stefan Weil writes:
> Am 14.07.2019 um 19:30 schrieb Peter Maydell:
> [...]
>> "Analyzer thinks this multiply can overflow
>> but in fact it's not possible" is quite a common false
>> positive cause...
>
>
> The analysers don't complain because a multiply can overflow.
>
> They complain because t
On Mon, 15 Jul 2019, at 12:06, Rashmica Gupta wrote:
> Sorry for the late reply! I agree with most of your feedback and will
> send out
> a v2 shortly with those changes. I have a few replies below
>
> [snip]
>
> > > +static const struct AspeedGPIO gpios[0x1f0] = {
> > > +/* Set ABCD */
>
Sorry for the late reply! I agree with most of your feedback and will
send out
a v2 shortly with those changes. I have a few replies below
[snip]
> > +static const struct AspeedGPIO gpios[0x1f0] = {
> > +/* Set ABCD */
> > +[GPIO_ABCD_DATA_VALUE] = {0, read_data_value,
> > _write_data_val
On Mon, Jul 15, 2019 at 10:05:49AM +0800, Wei Yang wrote:
>Commit 6b6712efccd3 ('ram: Split dirty bitmap by RAMBlock') changes the
>parameter of postcopy_send_discard_bm_ram(), while left the document
>part untouched.
>
>This patch correct the document and fix two typo by hand.
>
>Signed-off-by: We
Commit 6b6712efccd3 ('ram: Split dirty bitmap by RAMBlock') changes the
parameter of postcopy_send_discard_bm_ram(), while left the document
part untouched.
This patch correct the document and fix two typo by hand.
Signed-off-by: Wei Yang
---
v2: fix typo in function name, pointed by Dave
---
m
On Sun, Jul 14, 2019 at 10:51:19PM +0800, Ivan Ren wrote:
> Reproduce the problem:
> migrate
> migrate_cancel
> migrate
>
> Error happen for memory migration
Can mention "this mostly revert 0315851938 but with comments kept"
when merge...
>
> The reason as follows:
> 1. qemu start, ram_list.dir
On Sat, Jul 13, 2019 at 01:42:39AM +0800, Dr. David Alan Gilbert wrote:
> * Kirti Wankhede (kwankh...@nvidia.com) wrote:
> >
> >
> > On 7/11/2019 9:53 PM, Dr. David Alan Gilbert wrote:
> > > * Yan Zhao (yan.y.z...@intel.com) wrote:
> > >> On Thu, Jul 11, 2019 at 06:50:12PM +0800, Dr. David Alan G
On 7/12/19 9:34 AM, Alex Bennée wrote:
>
> Jan Bobek writes:
>
>> This is v3 of the patch series posted in [1] and [2]. Note that this
>> is the first fully-featured patch series implementing all desired
>> functionality, including (V)LDMXCSR and VSIB-based instructions like
>> VGATHER*.
>>
>> W
On 7/12/19 10:24 AM, Richard Henderson wrote:
> On 7/12/19 12:32 AM, Jan Bobek wrote:
>> +sub vex($%)
>> +{
>> +my ($insn, %vex) = @_;
>> +my $regidw = $is_x86_64 ? 4 : 3;
>> +
>> +# There is no point in randomizing other VEX fields, since
>> +# VEX.R/.X/.B are encoded automatically
If running full machine stack is an option, than I think that you will be
able to use SBSA machine in your tests once we have all the FW images
ready. But unfortunately we are not there yet.
niedz., 14 lip 2019, 23:57 użytkownik Guenter Roeck
napisał:
> On 7/14/19 8:40 AM, Radoslaw Biernacki wr
On 7/12/19 10:11 AM, Richard Henderson wrote:
> On 7/12/19 12:32 AM, Jan Bobek wrote:
>> The module risugen_x86_asm.pm exports named register constants and
>> asm_insn_* family of functions, which greatly simplify emission of x86
>> instructions.
>>
>> Signed-off-by: Jan Bobek
>> ---
>> risugen_x
On 7/14/19 8:40 AM, Radoslaw Biernacki wrote:
This machine is not ment for direct kernel boot. Is main purpose is development
of FW, kernel and other HW/SW parts for SBSA. We are currently working on UEFI
and ATF for this machine.
It might be somehow possible to run kernel with DT but we do no
On 7/12/19 1:48 AM, Richard Henderson wrote:
> On 7/12/19 12:32 AM, Jan Bobek wrote:
>> insnv allows emitting variable-length instructions in little-endian or
>> big-endian byte order; it subsumes functionality of former insn16()
>> and insn32() functions.
>>
>> randint can reliably generate signed
Public bug reported:
qemu-system-arm does not start with version >= 2.6 and KVM enabled.
cpu_address_space_init: Assertion `asidx == 0 || !kvm_enabled()'
failed.
Hardware is Odroid XU4 with Exynos with 4.9.61+ Tested with Debian
Stretch (9) or Buster (10).
Without KVM it is running fine but s
On Sun, Jul 14, 2019 at 3:54 PM Laurent Vivier wrote:
>
> From: Daniel P. Berrangé
>
> The SIOCGSTAMP symbol was previously defined in the
> asm-generic/sockios.h header file. QEMU sees that header
> indirectly via sys/socket.h
>
> In linux kernel commit 0768e17073dc527ccd18ed5f96ce85f9985e9115
>
Am 14.07.2019 um 19:30 schrieb Peter Maydell:
[...]
> "Analyzer thinks this multiply can overflow
> but in fact it's not possible" is quite a common false
> positive cause...
The analysers don't complain because a multiply can overflow.
They complain because the code indicates that a larger resu
On Sat, 13 Jul 2019 at 18:46, Stefan Weil wrote:
> LGTM reports 16 errors, 81 warnings and 119 recommendations:
> https://lgtm.com/projects/g/qemu/qemu/alerts/?mode=list.
I had a look at some of these before, but mostly I came
to the conclusion that it wasn't worth trying to put the
effort into k
Hi!
> On Jul 14, 2019, at 3:40 PM, Laurent Vivier wrote:
>
> Add --preserve-arg0 in qemu-binfmt-conf.sh to configure the preserve-arg0
> flag.
>
> Now, if QEMU is started with -0 or QEMU_ARGV0 and an empty parameter
> argv[0] (the full pathname provided by binfmt-misc) is removed and
> replaced
On 7/14/19 3:40 PM, Laurent Vivier wrote:
> filename is only used to open the file if AT_EXECFD is not provided.
> But exec_path already contains the path of the file to open.
> Remove filename as it is only used in main.c whereas exec_path is
> also used in syscall.c.
>
> Fixes: d088d664f201 ("li
Hi Paolo,
On 7/12/19 7:31 PM, Paolo Bonzini wrote:
> On 12/07/19 18:45, Philippe Mathieu-Daudé wrote:
>> On 7/12/19 4:58 PM, Paolo Bonzini wrote:
>>> The other is whether we want to enable USB_BLUETOOTH by default. I
>>> wouldn't have any problem there, but if we disable it basically no one
>>> w
This machine is not ment for direct kernel boot. Is main purpose is
development of FW, kernel and other HW/SW parts for SBSA. We are currently
working on UEFI and ATF for this machine.
It might be somehow possible to run kernel with DT but we do not support it
at this moment. If all you want is to
On 2019-07-10 21:58, Marc-André Lureau wrote:
> On Tue, Jul 9, 2019 at 10:49 PM Kővágó, Zoltán wrote:
>>
>> Pulseaudio normally assumes that when the server wants it, the client
>> can generate the audio samples and send it right away. Unfortunately
>> this is not the case with QEMU -- it's up to
Hi,
On Sun, Jun 30, 2019 at 06:20:32PM +0800, Hongbo Zhang wrote:
> For the Aarch64, there is one machine 'virt', it is primarily meant to
> run on KVM and execute virtualization workloads, but we need an
> environment as faithful as possible to physical hardware, to support
> firmware and OS dev
The problem still exists in mainline, Ping for review
On Tue, Jun 25, 2019 at 9:18 PM Ivan Ren wrote:
> The patches fix the problems encountered in multifd migration when try
> to cancel the migration by migrate_cancel.
>
> Ivan Ren (3):
> migration: fix migrate_cancel leads live_migration thr
On Thu, 2019-07-11 at 18:27 +0200, Stefano Garzarella wrote:
> On Thu, Jul 11, 2019 at 06:09:40PM +0300, Maxim Levitsky wrote:
> > preallocation=off and preallocation=metadata
> > both allocate luks header only, and preallocation=falloc/full
> > is passed to underlying file.
> >
> > Fixes: https:/
Reproduce the problem:
migrate
migrate_cancel
migrate
Error happen for memory migration
The reason as follows:
1. qemu start, ram_list.dirty_memory[DIRTY_MEMORY_MIGRATION] all set to
1 by a series of cpu_physical_memory_set_dirty_range
2. migration start:ram_init_bitmaps
- memory_global_dir
From: Daniel P. Berrangé
The SIOCGSTAMP symbol was previously defined in the
asm-generic/sockios.h header file. QEMU sees that header
indirectly via sys/socket.h
In linux kernel commit 0768e17073dc527ccd18ed5f96ce85f9985e9115
the asm-generic/sockios.h header no longer defines SIOCGSTAMP.
Instead
Add --preserve-arg0 in qemu-binfmt-conf.sh to configure the preserve-arg0
flag.
Now, if QEMU is started with -0 or QEMU_ARGV0 and an empty parameter
argv[0] (the full pathname provided by binfmt-misc) is removed and
replaced by argv[1] (the original argv[0] provided by binfmt-misc when
'P'/preserv
filename is only used to open the file if AT_EXECFD is not provided.
But exec_path already contains the path of the file to open.
Remove filename as it is only used in main.c whereas exec_path is
also used in syscall.c.
Fixes: d088d664f201 ("linux-user: identify running binary in /proc/self/exe")
Le 14/07/2019 à 13:33, Arnd Bergmann a écrit :
> On Sun, Jul 14, 2019 at 12:41 PM Richard Henderson
> wrote:
>>
>> On 7/12/19 3:55 PM, Arnd Bergmann wrote:
>>> glibc will have to create a definition that matches the kernel, which uses
>>>
>>> struct __kernel_timespec {
>>> __s64 tv_sec;
>>>
Am 13.07.2019 um 21:42 schrieb Paolo Bonzini:
> On 13/07/19 19:46, Stefan Weil wrote:
>> LGTM reports 16 errors, 81 warnings and 119 recommendations:
>> https://lgtm.com/projects/g/qemu/qemu/alerts/?mode=list.
>>
>> Some of them are already known (wrong format strings), others look like
>> real err
The Milkymist SoftUSB block provides the OHCI USB standard
(missed in 0858746b835).
Signed-off-by: Philippe Mathieu-Daudé
---
hw/lm32/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/lm32/Kconfig b/hw/lm32/Kconfig
index 3d09c2dd6f..ed2e3060b0 100644
--- a/hw/lm32/Kconfig
+++ b/hw/l
On Sun, Jul 14, 2019 at 12:41 PM Richard Henderson
wrote:
>
> On 7/12/19 3:55 PM, Arnd Bergmann wrote:
> > glibc will have to create a definition that matches the kernel, which uses
> >
> > struct __kernel_timespec {
> > __s64 tv_sec;
> > __s64 tv_nsec;
> > };
> >
> > As posix requires tv_
This code block is already surrounded by #ifndef CODE_ACCESS.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
include/exec/cpu_ldst_useronly_template.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/exec/cpu_ldst_useronly_template.h
b/include/exec/cpu_ldst_useronly_
Turn helper_retaddr into a multi-state flag that may now also
indicate when we're performing a read on behalf of the translator.
In this case, release the mmap_lock before the longjmp back to
the main cpu loop, and thereby avoid a failing assert therein.
Fixes: https://bugs.launchpad.net/qemu/+bug
At present we have a potential error in that helper_retaddr contains
data for handle_cpu_signal, but we have not ensured that those stores
will be scheduled properly before the operation that may fault.
It might be that these races are not in practice observable, due to
our use of -fno-strict-alia
This patch fixes two problems:
(1) The inputs to the EXTR insn were reversed,
(2) The input constraints use rZ, which means that we need to use
the REG0 macro in order to supply XZR for a constant 0 input.
Fixes: 464c2969d5d
Reported-by: Peter Maydell
Tested-by: Alex Bennée
Reviewed-by: Alex
These functions are not used, and are not usable in the
context of code generation, because we never have a helper
return address to pass in to them.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
include/exec/cpu_ldst_useronly_template.h | 6 +-
1 file changed, 5 insertions(
We have some potential race conditions vs our user-exec signal
handler that will be solved with this barrier.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
include/qemu/atomic.h | 11 +++
1 file changed, 11 insertions(+)
diff --git a/include/qemu/atomic.h b/include/qemu
The following changes since commit 1316b1ddc8a05e418c8134243f8bff8cccbbccb1:
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging
(2019-07-12 15:38:22 +0100)
are available in the Git repository at:
https://github.com/rth7680/qemu.git tags/pull-tcg-2019071
On a 64-bit host, discard any replications of the 32-bit
sign bit when performing the shift and merge.
Fixes: https://bugs.launchpad.net/bugs/1834496
Tested-by: Christophe Lyon
Tested-by: Alex Bennée
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
tcg/optimize.c | 4 ++--
1 file
On 7/12/19 3:39 PM, Philippe Mathieu-Daudé wrote:
> A series of obvious patches to build without the deprecated
> bluetooth devices. Still worth for 4.1 or too late?
> It is clearly not a bugfix.
>
> Regards,
>
> Phil.
>
> Philippe Mathieu-Daudé (7):
> hw/arm: Nokia N-series tablet requires Bl
On 7/12/19 3:55 PM, Arnd Bergmann wrote:
> glibc will have to create a definition that matches the kernel, which uses
>
> struct __kernel_timespec {
> __s64 tv_sec;
> __s64 tv_nsec;
> };
>
> As posix requires tv_nsec to be 'long', you need padding between
> tv_sec and tv_nsec to have a li
56 matches
Mail list logo
