Launchpad has imported 9 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=109695.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
In preparation for a split of the memory map into a static
part and a dynamic part floating after the RAM, let's rename the
regions located after the RAM
Signed-off-by: Eric Auger
Reviewed-by: Peter Maydell
Reviewed-by: Igor Mammedov
---
v8:
- added Igor's R-b and fixed "line over 80 character
Now we have the extended memory map (high IO regions beyond the
scalable RAM) and dynamic IPA range support at KVM/ARM level
we can bump the legacy 255GB initial RAM limit. The actual maximum
RAM size now depends on the physical CPU and host kernel, in
accelerated mode. In TCG mode, it depends on t
From: Shameer Kolothum
We introduce an helper to create a memory node.
Signed-off-by: Eric Auger
Signed-off-by: Shameer Kolothum
Reviewed-by: Igor Mammedov
---
v7 -> v8:
- Added Igor's R-b
v6 -> v7:
- msg error in the caller
- add comment about NUMA ID
---
hw/arm/boot.c | 54 ++
Up to now the memory map has been static and the high IO region
base has always been 256GiB.
This patch modifies the virt_set_memmap() function, which freezes
the memory map, so that the high IO range base becomes floating,
located after the initial RAM and the device memory.
The function compute
Add support to our configure and makefile machinery for building
our rST docs into HTML files.
Building the documentation now requires that sphinx-build is
available; this seems better than allowing half the docs to
be built if it is not present but having half of them missing.
(In particular it m
Hi,
When we build qemu with "-Wmaybe-uninitialized" on, and got the following error
information.
CC qobject/json-streamer.o
CC qobject/json-parser.o
CC qobject/block-qdict.o
qobject/block-qdict.c: In function 'qdict_array_split':
qobject/block-qdict.c:259:25: error: 'subqdict
Add the kvm_arm_get_max_vm_ipa_size() helper that returns the
number of bits in the IPA address space supported by KVM.
This capability needs to be known to create the VM with a
specific IPA max size (kvm_type passed along KVM_CREATE_VM ioctl.
Signed-off-by: Eric Auger
---
v6 -> v7:
- s/kvm_arm
We are about to allow the memory map to grow beyond 1TB and
potentially overshoot the VCPU AA64MMFR0.PARANGE.
In aarch64 mode and when highmem is set, let's check the VCPU
PA range is sufficient to address the highest GPA of the memory
map.
Signed-off-by: Eric Auger
---
hw/arm/virt.c | 17 +
Don't hard-code the QEMU version number into conf.py. Instead
we either pass it to sphinx-build on the command line, or
(if doing a standalone Sphinx run in a readthedocs.org setup)
extract it from the VERSION file.
Signed-off-by: Peter Maydell
Reviewed-by: Alex Bennée
---
Makefile | 2 +-
On Wed, Feb 27, 2019 at 06:37:14PM +0100, Kevin Wolf wrote:
> Am 27.02.2019 um 17:52 hat Sergio Lopez geschrieben:
> > Stopping the dataplane requires calling to blk_set_aio_context, which
> > may need to wait for a running job to be completed or paused.
> >
> > As stopping the dataplane is someth
On ARM, the kvm_type will be resolved by querying the KVMState.
Let's add the MachineState handle to the callback so that we
can retrieve the KVMState handle. in kvm_init, when the callback
is called, the kvm_state variable is not yet set.
Signed-off-by: Eric Auger
Acked-by: David Gibson
[ppc p
The machine RAM attributes will need to be analyzed during the
configure_accelerator() process. especially kvm_type() arm64
machine callback will use them to know how many IPA/GPA bits are
needed to model the whole RAM range. So let's assign those machine
state fields before calling configure_accel
By default Sphinx wants to build a single manual at once.
For QEMU, this doesn't suit us, because we want to have
separate manuals for "Developer's Guide", "User Manual",
and so on, and we don't want to ship the Developer's Guide
to end-users. However, we don't want to completely duplicate
conf.py
Abstract out the "identify the pkgversion" code from the
rule for creating qemu-version.h, so it sets makefile
variables for QEMU_PKGVERSION and QEMU_FULL_VERSION.
(We will want to use these when building the Sphinx docs.)
Signed-off-by: Peter Maydell
Reviewed-by: Alex Bennée
---
Makefile | 33
sphinx-build complains about using :option: to mark up option
flags that it doesn't know about (because they were not defined
using the "option::" directive):
docs/pr-manager.rst:68: WARNING: unknown option: -d
Suppress these warnings. This way we get the semantic markup
of the option flag but no
Convert the memory API documentation from plain text
to restructured text format.
This is a very minimal conversion: all I had to change
was to mark up the ASCII art parts as Sphinx expects
for 'literal blocks', and fix up the bulleted lists
(Sphinx expects no leading space before the bullet, and
Add the 'navigation' bar to the sidebar, which for some
reason is not enabled by default. Remove 'relations', which
is effectively disabled anyway and isn't useful for us.
Signed-off-by: Peter Maydell
Reviewed-by: Alex Bennée
---
docs/conf.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletio
Sphinx defaults to including all the rST source files
in the HTML build and making each HTML page link to the
source file. Disable that.
Signed-off-by: Peter Maydell
Reviewed-by: Alex Bennée
---
docs/conf.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/docs/conf.py b/docs/conf.py
inde
This patchset enables building and installing the various rST
docs we have started to accumulate in our docs/ directory.
It does this using Sphinx (which is the docs tooling that the
Linux kernel uses). The series is not trying to take us in one
giant leap to a brave new Sphinx-powered world -- it
Commit the initial Sphinx conf.py and skeleton index.rst as
generated with sphinx-quickstart. We'll update these to
add QEMU-specific tweaks in subsequent commits.
Signed-off-by: Peter Maydell
---
docs/conf.py | 168 +
docs/index.rst | 20 ++
We don't yet have any custom static files, so disable this
config file setting to avoid a warning from sphinx about
not being able to find the directory.
Signed-off-by: Peter Maydell
Reviewed-by: Alex Bennée
---
docs/conf.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
sphinx-build complains:
docs/cpu-hotplug.rst:67: ERROR: Unexpected indentation.
docs/cpu-hotplug.rst:69: ERROR: Unexpected indentation.
docs/cpu-hotplug.rst:74: WARNING: Block quote ends without a blank line;
unexpected unindent.
docs/cpu-hotplug.rst:75: WARNING: Block quote ends without a blank
On Mon, 25 Feb 2019 09:25:29 +0800
Wei Yang wrote:
> We didn't specify the indent rule for multiline code here, which may
> mislead users. And in current code, the code use different rules.
diffrent from what? I'd use "various styles"
>
> Add this rule in CODING_STYLE to make sure this is clear
On Mon, 18 Feb 2019 13:26:55 +0100
David Hildenbrand wrote:
> This series is based on the patches currently on the list:
> - [PATCH v2] softfloat: add float128_is_{normal,denormal}
> - [PATCH v1] softfloat: Implement float128_to_uint32
> - [PATCH v2] softfloat: Support float_round_to_odd more pl
Fix has been merged:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=83c68e149a9365a3db6de
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/181752
On Thu, 28 Feb 2019 at 14:00, Eric Blake wrote:
>
> On 2/28/19 7:42 AM, Aarushi Mehta wrote:
> > Hi
> >
> > This is a trivial contribution part of the BiteSizedTasks on the wiki.
> > I found this discussion
> > http://git.corpit.ru/?p=qemu.git;a=commit;h=b45c03f585ea9bb1af76c73e82195418c294919d
>
Intel vt-d rev3.0 [1] introduces a new translation mode called
'scalable mode', which enables PASID-granular translations for
first level, second level, nested and pass-through modes. The
vt-d scalable mode is the key ingredient to enable Scalable I/O
Virtualization (Scalable IOV) [2] [3], which al
From: "Liu, Yi L"
Intel(R) VT-d 3.0 spec introduces scalable mode address translation to
replace extended context mode. This patch extends current emulator to
support Scalable Mode which includes root table, context table and new
pasid table format change. Now intel_iommu emulates both legacy mod
This patch adds an option to provide flexibility for user to expose
Scalable Mode to guest. User could expose Scalable Mode to guest by
the config as below:
"-device intel-iommu,caching-mode=on,scalable-mode=on"
The Linux iommu driver has supported scalable mode. Please refer below
patch set:
From: "Liu, Yi L"
Per Intel(R) VT-d 3.0, the qi_desc is 256 bits in Scalable
Mode. This patch adds emulation of 256bits qi_desc.
Signed-off-by: Liu, Yi L
[Yi Sun is co-developer to rebase and refine the patch.]
Signed-off-by: Yi Sun
---
v2:
- modify s-o-b position.
- remove unnecessary
Further debugging on IRC reveals that QEMU itself is not hanging, but
the guest code is looping infinitely, because QEMU doesn't implement the
AVX instruction set and isn't generating an undefined-instruction
exception either. So the %rdx output from the AVX insn is wrong and the
guest code never e
** Summary changed:
- qemu-user-x86-64 hangs at vcvttsd2si
+ qemu x86 TCG doesn't support AVX insns
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1818075
Title:
qemu x86 TCG doesn't support AVX in
my guess is we're doing something unhelpful with the AVX insn,
and so the guest code which is checking the result and using it as its
loop condition for the jns is just looping forever
in_asm log just stopped with this as the last line
0x4000b4ef4a: 79 9ejns 0x4000b4ee
Hi Andrew,
That's great news, I'll then bring those drivers up to the modern qemu API!
Maybe that's a Linux kernel module configuration issue as well, but
with the BCM System Timer small delays depend on polling the counter.
Without the qemu support that counter register remains zero, causing
an
On Thu, 28 Feb 2019 09:13:25 +0800
Wei Yang wrote:
> On Wed, Feb 27, 2019 at 07:04:02PM +0100, Igor Mammedov wrote:
> >On Mon, 25 Feb 2019 09:15:34 +0800
> >Wei Yang wrote:
> >
> >> On Mon, Feb 25, 2019 at 09:07:08AM +0800, Wei Yang wrote:
> >> >Currently we do device realization like below:
On Thu, Feb 21, 2019 at 10:18:52AM +0200, Yuri Benditovich wrote:
> On Thu, Feb 21, 2019 at 8:49 AM Jason Wang wrote:
> >
> >
> > On 2019/2/21 下午2:00, Yuri Benditovich wrote:
> > > On Tue, Feb 19, 2019 at 8:27 AM Jason Wang wrote:
> > >>
> > >> On 2019/2/19 上午7:34, Michael S. Tsirkin wrote:
> > >
On Thu, 28 Feb 2019 08:48:18 +0100
Auger Eric wrote:
> Hi Igor, Shameer,
>
> On 2/27/19 6:51 PM, Igor Mammedov wrote:
> > On Wed, 27 Feb 2019 10:41:45 +
> > Shameerali Kolothum Thodi wrote:
> >
> >> Hi Eric,
> >>
> >>> -Original Message-
> >>> From: Auger Eric [mailto:eric.au..
> -Original Message-
> From: Shameerali Kolothum Thodi
> Sent: 28 February 2019 12:04
> To: 'Auger Eric' ; Laszlo Ersek ;
> shannon.zha...@gmail.com; peter.mayd...@linaro.org;
> imamm...@redhat.com; qemu-devel@nongnu.org; qemu-...@nongnu.org
> Cc: xuwei (O) ; Linuxarm ; Ard
> Biesheuvel ;
28.02.2019 16:44, Eric Blake wrote:
> On 2/28/19 4:13 AM, Vladimir Sementsov-Ogievskiy wrote:
>
>> +++ b/qapi/block-core.json
>> @@ -470,12 +470,16 @@
>> # @persistent: true if the bitmap will eventually be flushed to
>> persistent
>> # storage (since 4.0)
Public bug reported:
I'm trying to execute code that has been built with -march=skylake
-mtune=generic -mavx2 under qemu-user x86-64 with -cpu Skylake-Client.
However this code just hangs at 100% CPU.
Adding input tracing shows that it is likely hanging when dealing with
an AVX instruction:
warn
On 2/28/19 7:42 AM, Aarushi Mehta wrote:
> Hi
>
> This is a trivial contribution part of the BiteSizedTasks on the wiki.
> I found this discussion
> http://git.corpit.ru/?p=qemu.git;a=commit;h=b45c03f585ea9bb1af76c73e82195418c294919d
> on migrating even g_malloc to g_new, is this not appropriate
On Thu, 28 Feb 2019 08:46:10 +0800
Wei Yang wrote:
> On Wed, Feb 27, 2019 at 06:27:49PM +0100, Igor Mammedov wrote:
> >On Wed, 27 Feb 2019 13:59:20 +
> >Wei Yang wrote:
> >
> >> On Wed, Feb 27, 2019 at 02:12:42PM +0100, Igor Mammedov wrote:
> >> >On Mon, 25 Feb 2019 12:47:14 +
> >> >
On Thu, Feb 28, 2019 at 07:12:45PM +0530, Aarushi Mehta wrote:
> Hi
>
> This is a trivial contribution part of the BiteSizedTasks on the wiki.
> I found this discussion
> http://git.corpit.ru/?p=qemu.git;a=commit;h=b45c03f585ea9bb1af76c73e82195418c294919d
> on migrating even g_malloc to g_new, is
On Thu, 28 Feb 2019 13:28:47 +0100
David Hildenbrand wrote:
> When unplugging a device, at one point the device will be destroyed
> via object_unparent(). This will, one the one hand, unrealize the
> removed device hierarchy, and on the other hand, destroy/free the
> device hierarchy.
>
> When c
On 2/28/19 4:13 AM, Vladimir Sementsov-Ogievskiy wrote:
> +++ b/qapi/block-core.json
> @@ -470,12 +470,16 @@
> # @persistent: true if the bitmap will eventually be flushed to
> persistent
> # storage (since 4.0)
>>>
>>> so, bitmap can't be inconsistent and p
On Thu, 28 Feb 2019 13:27:54 +0100
Laszlo Ersek wrote:
> On 02/28/19 11:12, Auger Eric wrote:
> > Hi Laszlo,
> >
> > On 2/27/19 9:14 PM, Laszlo Ersek wrote:
> >> On 02/27/19 13:55, Shameerali Kolothum Thodi wrote:
> >>> Hi Laszlo,
> >>>
> -Original Message-
> From: Shamee
Hi
This is a trivial contribution part of the BiteSizedTasks on the wiki.
I found this discussion
http://git.corpit.ru/?p=qemu.git;a=commit;h=b45c03f585ea9bb1af76c73e82195418c294919d
on migrating even g_malloc to g_new, is this not appropriate for the same?
The wiki can presumably use an update
On Fri, 1 Feb 2019 at 16:43, Alex Bennée wrote:
>
>
> Peter Maydell writes:
>
> > Add the 'navigation' bar to the sidebar, which for some
> > reason is not enabled by default. Remove 'relations', which
> > is effectively disabled anyway and isn't useful for us.
>
> I'm not sure what the title mea
On Thu, Feb 14, 2019 at 03:39:11PM +1100, David Gibson wrote:
> I posted some RFCs for this back in December, but didn't wrap it up in
> time for 3.1. Posting again for inclusion in 4.0.
>
> The virtio-balloon devices was never really thought out for cases
> other than 4kiB pagesize on both guest
On Thu, Feb 14, 2019 at 03:39:12PM +1100, David Gibson wrote:
> When the balloon is inflated, we discard memory place in it using madvise()
> with MADV_DONTNEED. And when we deflate it we use MADV_WILLNEED, which
> sounds like it makes sense but is actually unnecessary.
>
> The misleadingly named
Hi Laszlo,
On 2/28/19 1:27 PM, Laszlo Ersek wrote:
> On 02/28/19 11:12, Auger Eric wrote:
>> Hi Laszlo,
>>
>> On 2/27/19 9:14 PM, Laszlo Ersek wrote:
>>> On 02/27/19 13:55, Shameerali Kolothum Thodi wrote:
Hi Laszlo,
> -Original Message-
> From: Shameerali Kolothum Thodi
>
-Original Message-
From: Dr. David Alan Gilbert [mailto:dgilb...@redhat.com]
Sent: Thursday, February 28, 2019 9:03 PM
To: Zhang, Chen
Cc: Li Zhijian ; Zhang Chen ;
Juan Quintela ; zhanghailiang
; qemu-dev
Subject: Re: [PATCH 2/3] Migration/colo.c: Fix COLO failover status error
*
On Fri, 4 Jan 2019 at 05:22, David Gibson wrote:
>
> On Fri, Jan 04, 2019 at 12:44:59AM +0100, Alexander Graf wrote:
> >
> >
> > On 03.01.19 18:38, Peter Maydell wrote:
> > > Hi; currently we ship with a u-boot.e500 which is from u-boot
> > > v2017.07. It would be nice to move that forward, specif
* Zhang, Chen (chen.zh...@intel.com) wrote:
>
> -Original Message-
> From: Dr. David Alan Gilbert [mailto:dgilb...@redhat.com]
> Sent: Tuesday, February 26, 2019 6:55 PM
> To: Zhang, Chen
> Cc: Li Zhijian ; Zhang Chen ;
> Juan Quintela ; zhanghailiang
> ; qemu-dev
> Subject: Re: [PATC
On Tue, 26 Feb 2019 at 16:56, Eric Blake wrote:
>
> The following changes since commit d88d85f1f0625d57e9f354aa0874c4c8b5d1fb47:
>
> Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request'
> into staging (2019-02-25 17:28:04 +)
>
> are available in the Git repository at:
>
>
enum resource_type {
RES_REGFILE,
RES_STATE,
+RES_MAX,
};
static uint32_t encode_resource(enum resource_type r, unsigned g, unsigned n)
{
-assert(r < 256 && g < 256 && n < 65536);
+assert(r < RES_MAX && g < 256 && n < 65536);
return (r << 24) | (g << 16) | n;
}
and pushed the updated tag 20190228-xtensa.
--
Thanks.
-- Max
On Thu, 28 Feb 2019 10:57:41 +0100
Auger Eric wrote:
> Hi Igor,
>
> On 2/27/19 6:14 PM, Igor Mammedov wrote:
> > On Mon, 28 Jan 2019 11:05:45 +
> > Shameer Kolothum wrote:
> >
> >> pc-dimm memory hotplug is enabled using GPIO(Pin 2) based ACPI
> >> event. Hot removal functionality is not
From: Philippe Mathieu-Daudé
Due to a misuse of rules.mak logical functions, commit f386df17448
disabled the guest-agent test.
Enable it back.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Thomas Huth
Reviewed-by: Laurent Vivier
Signed-off-by: Thomas Huth
---
tests/Makefile.include | 2
Let's use a wrapper instead of looking it up manually. This function can
than be reused when we explicitly want to have the bus hotplug handler
(e.g. when the bus hotplug handler was overwritten by the machine
hotplug handler).
Reviewed-by: Igor Mammedov
Signed-off-by: David Hildenbrand
---
hw/
From: Philippe Mathieu-Daudé
Richard obviously maintains this subdirectory, make this official :)
Remove the qemu-devel@nongnu.org entry because the list is always
selected by the 'All patches CC here' section.
Cc: Richard Henderson
Signed-off-by: Philippe Mathieu-Daudé
Signed-off-by: Thomas
These files / devices are only used by SPARC machines, so we can sort
them into the corresponding category in the MAINTAINERS file.
Cc: Mark Cave-Ayland
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Thomas Huth
---
MAINTAINERS | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
The e-mail address m...@sifive.com of Michael is not valid anymore.
Commit 7d04ac38959f8115f2a02 removed the entry already from the main
RISC-V section, but apparently forgot to remove it from the TCG
backend section, too.
Fixes: 7d04ac38959f8115f2a029d81db1c8aac179aa95
Reviewed-by: Palmer Dabbelt
From: Igor Mammedov
it will allow to return another hotplug handler than the default
one for a specific bus based device type. Which is needed to handle
non trivial plug/unplug sequences that need the access to resources
configured outside of bus where device is attached.
That will allow for ret
On 02/28/19 11:12, Auger Eric wrote:
> Hi Laszlo,
>
> On 2/27/19 9:14 PM, Laszlo Ersek wrote:
>> On 02/27/19 13:55, Shameerali Kolothum Thodi wrote:
>>> Hi Laszlo,
>>>
-Original Message-
From: Shameerali Kolothum Thodi
Sent: 25 February 2019 09:54
To: 'Laszlo Ersek' ; A
From: Philippe Mathieu-Daudé
Add Paolo as maintainer of the POSIX subsystem.
Remove the qemu-devel@nongnu.org entry because the list is always
selected by the 'All patches CC here' section.
Cc: Paolo Bonzini
Suggested-by: Markus Armbruster
Signed-off-by: Philippe Mathieu-Daudé
Signed-off-by:
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Thu, Feb 28, 2019 at 11:40:19AM +, Dr. David Alan Gilbert wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > On Wed, Feb 27, 2019 at 04:49:00PM +, Dr. David Alan Gilbert (git)
> > > wrote:
> > > > From: "Dr. David Alan Gilbert"
>
When unplugging a device, at one point the device will be destroyed
via object_unparent(). This will, one the one hand, unrealize the
removed device hierarchy, and on the other hand, destroy/free the
device hierarchy.
When chaining hotplug handlers, we want to overwrite a bus hotplug
handler by th
From: Philippe Mathieu-Daudé
Add Richard as maintainer, and Helge as reviewer.
Cc: Richard Henderson
Cc: Helge Deller
Signed-off-by: Philippe Mathieu-Daudé
[thuth: Add the machine entry alphabetically]
Signed-off-by: Thomas Huth
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Thomas Huth
Reviewed-by: Markus Armbruster
Signed-off-by: Thomas Huth
---
MAINTAINERS | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3a034f9..4e38864 1006
From: Philippe Mathieu-Daudé
Add Michael, Cornelia and Paolo as maintainers of the Linux subsystem.
Remove the qemu-devel@nongnu.org entry because the list is always
selected by the 'All patches CC here' section.
Suggested-by: Paolo Bonzini
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: Corn
Can somebody please pick this up in the near future? (@Eduardo, @MST,
@Paolo, @David - I have no idea who the right person is :) )
The longer we wait, the more likely it is that some stuff gets upstreamed
that conflicts with patch 1 and will break unnoticed. (e.g. spapr PHB
hotplug was just upstre
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Thomas Huth
---
MAINTAINERS | 4
1 file changed, 4 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 22e0293..3a034f9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
From: Philippe Mathieu-Daudé
Acked-by: Daniel P. Berrangé
Signed-off-by: Philippe Mathieu-Daudé
Signed-off-by: Thomas Huth
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4e38864..d81f9c4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2069
From: Thomas Huth
The MCF5208EVB supports 2 MiB of flash at address 0. Add support
for this memory region and some code to load the file that can
be specified with the "-bios" command line option.
This can be used for example to load U-Boot images for the
MCF5208EVB (we still lack some features i
From: Philippe Mathieu-Daudé
Nobody is looking at those files, downgrade this subsystem as orphan.
Remove the qemu-devel@nongnu.org entry because the list is always
selected by the 'All patches CC here' section.
Suggested-by: Markus Armbruster
Signed-off-by: Philippe Mathieu-Daudé
Signed-off-
From: Philippe Mathieu-Daudé
Reviewed-by: Mark Cave-Ayland
Signed-off-by: Philippe Mathieu-Daudé
Signed-off-by: Thomas Huth
---
MAINTAINERS | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8f9f9d7..22e0293 100644
--- a/MAINTAINERS
+++ b/
Hi Peter,
the following changes since commit adf2e451f357e993f173ba9b4176dbf3e65fee7e:
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging
(2019-02-26 19:04:47 +)
are available in the git repository at:
https://gitlab.com/huth/qemu.git tags/pull-request-2019-02
> -Original Message-
> From: Igor Mammedov [mailto:imamm...@redhat.com]
> Sent: 27 February 2019 17:14
> To: Shameerali Kolothum Thodi
> Cc: eric.au...@redhat.com; shannon.zha...@gmail.com;
> peter.mayd...@linaro.org; qemu-devel@nongnu.org; qemu-...@nongnu.org;
> Linuxarm ; xuwei (O)
>
> -Original Message-
> From: Igor Mammedov [mailto:imamm...@redhat.com]
> Sent: 27 February 2019 16:28
> To: Shameerali Kolothum Thodi
> Cc: eric.au...@redhat.com; shannon.zha...@gmail.com;
> peter.mayd...@linaro.org; qemu-devel@nongnu.org; qemu-...@nongnu.org;
> xuwei (O) ; Linuxarm
>
> -Original Message-
> From: Auger Eric [mailto:eric.au...@redhat.com]
> Sent: 28 February 2019 10:12
> To: Laszlo Ersek ; Shameerali Kolothum Thodi
> ; shannon.zha...@gmail.com;
> peter.mayd...@linaro.org; imamm...@redhat.com; qemu-devel@nongnu.org;
> qemu-...@nongnu.org
> Cc: xuwei (O)
On Tue, 26 Feb 2019 at 14:12, Alex Bennée wrote:
>
> The following changes since commit ef80b99ce7ffbd66b3efd493f4ca99f8abf59e79:
>
> Merge remote-tracking branch
> 'remotes/stsquad/tags/pull-testing-next-220219-1' into staging (2019-02-25
> 14:04:20 +)
>
> are available in the Git reposit
On Thu, Feb 28, 2019 at 11:40:19AM +, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > On Wed, Feb 27, 2019 at 04:49:00PM +, Dr. David Alan Gilbert (git)
> > wrote:
> > > From: "Dr. David Alan Gilbert"
> > >
> > > Currently we cleanup the migration object as we e
Sometimes sorecvfrom() is called from slirp.c because revents == G_IO_IN,
however inside sorecvfrom() function, ioctlsocket() returns 0 bytes available
and recvfrom could be blocking indefinitely. This adds a non-blocking flag to
recvfrom and checks data availability.
---
slirp/socket.c | 4 +++-
* Peter Xu (pet...@redhat.com) wrote:
> On Wed, Feb 27, 2019 at 04:49:00PM +, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Currently we cleanup the migration object as we exit main after the
> > main_loop finishes; however if there's a migration running thing
Patchew URL:
https://patchew.org/QEMU/20190228110835.16159-1-peter.mayd...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20190228110835.16159-1-peter.mayd...@linaro.org
Subject: [Qemu-devel] [PULL 00/16] target-arm que
On Tue, 26 Feb 2019 at 04:53, David Gibson wrote:
>
> The following changes since commit ef80b99ce7ffbd66b3efd493f4ca99f8abf59e79:
>
> Merge remote-tracking branch
> 'remotes/stsquad/tags/pull-testing-next-220219-1' into staging (2019-02-25
> 14:04:20 +)
>
> are available in the Git reposi
From: Richard Henderson
Signed-off-by: Richard Henderson
Message-id: 20190219222952.22183-6-richard.hender...@linaro.org
Reviewed-by: Peter Maydell
Signed-off-by: Peter Maydell
---
linux-user/elfload.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/linux-user/elfload.c b/linux-user/elf
From: Richard Henderson
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
Message-id: 20190219222952.22183-5-richard.hender...@linaro.org
Signed-off-by: Peter Maydell
---
target/arm/cpu.c | 1 +
target/arm/cpu64.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/target/arm/c
Hi,
On Thu, Feb 28, 2019 at 11:45 AM llyzs wrote:
>
> Hi,
>
> I am having a guest freeze issue (win10), and through debugging I found out
> that sometimes sorecvfrom() is called from slirp.c because revents ==
> G_IO_IN, however inside sorecvfrom() function, ioctlsocket() returns 0
> bytes availa
Found out that the guest freeze issue is due to a block udp reading call
rather than a deaklock. I have rephase the bug description and sent a
patch in qemu-devel.
** Summary changed:
- deadlock in prepare_mmio_access reading mmio
+ sorecvfrom freezes guest
** Description changed:
QEMU releas
From: Richard Henderson
Signed-off-by: Richard Henderson
Message-id: 20190219222952.22183-4-richard.hender...@linaro.org
Reviewed-by: Peter Maydell
Signed-off-by: Peter Maydell
---
target/arm/cpu.h | 5 ++
target/arm/translate.c | 129 ++---
2 files
This reverts commit 823e1b3818f9b10b824ddcd756983b6e2fa68730,
which introduces a regression running EDK2 guest firmware
under KVM:
error: kvm run failed Function not implemented
PC=00013f5a6208 X00=404003c4 X01=003a
X02= X03=404003c4 X04=000
From: Richard Henderson
Signed-off-by: Richard Henderson
Message-id: 20190219222952.22183-3-richard.hender...@linaro.org
Reviewed-by: Peter Maydell
Signed-off-by: Peter Maydell
---
target/arm/cpu.h | 5
target/arm/translate-a64.c | 49 +-
2
Create and connect the MHUs in the SSE-200.
Signed-off-by: Peter Maydell
Reviewed-by: Richard Henderson
Message-id: 20190219125808.25174-3-peter.mayd...@linaro.org
---
include/hw/arm/armsse.h | 3 ++-
hw/arm/armsse.c | 40 ++--
2 files changed, 32 in
From: Richard Henderson
Note that float16_to_float32 rightly squashes SNaN to QNaN.
But of course pickNaNMulAdd, for ARM, selects SNaNs first.
So we have to preserve SNaN long enough for the correct NaN
to be selected. Thus float16_to_float32_by_bits.
Signed-off-by: Richard Henderson
Message-i
The CPUWAIT register acts as a sort of power-control: if a bit
in it is 1 then the CPU will have been forced into waiting
when the system was reset (which in QEMU we model as the
CPU starting powered off). Writing a 0 to the register will
allow the CPU to boot (for QEMU, we model this as powering
i
At the moment the handling of init-svtor and cpuwait initial
values is split between armsse.c and iotkit-sysctl.c:
the code in armsse.c sets the initial state of the CPU
object by setting the init-svtor and start-powered-off
properties, but the iotkit-sysctl.c code has its own
code setting the rese
There is a set of VFP instructions which we implement in
disas_vfp_v8_insn() and gate on the ARM_FEATURE_V8 bit.
These were all first introduced in v8 for A-profile, but in
M-profile they appeared in v7M. Gate them on the MVFR2
FPMisc field instead, and rename the function appropriately.
Signed-of
Make the M-profile "init-svtor" property be settable after realize.
This matches the hardware, where this is a config signal which
is sampled on CPU reset and can thus be changed between one
reset and another. To do this we have to change the API we
use to add the property.
(We will need this capa
201 - 300 of 366 matches
Mail list logo
