On Mon, Apr 16, 2018 at 03:52:03PM -0700, Alexander Kappner wrote:
> Hi Gerd,
>
> thanks for reviewing. I'll follow up with a v3 of the patch addressing your
> proposed changes.
>
> >> This allows a QMP client to query which USB devices may be available
> >> for redirection.
>
> > At least libv
On Mon, Apr 16, 2018 at 05:17:32PM +0800, Peter Xu wrote:
> On Mon, Apr 16, 2018 at 04:37:48PM +0800, Stefan Hajnoczi wrote:
> > On Thu, Apr 12, 2018 at 02:11:08PM +0800, Peter Xu wrote:
> > > In the future the monitor iothread may be accessing the cur_mon as
> > > well (via monitor_qmp_dispatch_on
This series contains a number of cleanups to the way we set up and
start a guest in PAPR mode.
Applies on top of my ppc-for-2.13 branch.
David Gibson (10):
spapr: Avoid redundant calls to spapr_cpu_reset()
spapr: Remove support for PowerPC 970 with pseries machine type
target/ppc: Remove un
af81cf323c1 "spapr: CPU hotplug support" added a direct call to
spapr_cpu_reset() in spapr_cpu_init(), as well as registering it as a
reset callback. That was in order to make sure that the reset function
got called for a newly hotplugged cpu, which would miss the global machine
reset.
However, t
cpu_ppc_set_papr() has code to make sure the LPCR and AMOR (hypervisor
privileged registers) have values which will make TCG behave correctly for
paravirtualized guests, where we don't emulate the cpu when in hypervisor
mode.
It does this by mangling the default values of the SPRs, so that they wi
Current POWER cpus allow for a VRMA, a special mapping which describes a
guest's view of memory when in real mode (MMU off, from the guest's point
of view). Older cpus didn't have that which meant that to support a guest
a special host-contiguous region of memory was needed to give the guest its
R
cpu_ppc_set_papr() does three things: 1) it sets up the virtual hypervisor
interface, 2) it prevents the cpu from ever entering hypervisor mode and
3) it tells KVM that we're emulating a cpu in PAPR mode.
(1) & (2) make sense for any virtual hypervisor (if one ever exists). (3)
belongs more prope
In cpu_ppc_set_papr() the UPRT and GTSE bits of the LPCR are initialized
based on on ppc64_radix_guest(). Which seems reasonable, except that
ppc64_radix_guest() is based on spapr->patb_entry which is only set up
in spapr_machine_reset, called much later than cpu_ppc_set_papr().
So the initializa
To prevent spurious wakeups on cpus that are supposed to be disabled, we
need to clear the LPCR bits which control certain wakeup events.
spapr_cpu_reset() has separate cases here for boot and non-boot (initially
inactive) cpus. rtas_start_cpu() then turns the LPCR bits on when the
non-boot cpus a
Although the order doesn't really matter at the moment, it's possible
other initializastions could depend on the compatiblity mode, so make sure
we set it first in spapr_cpu_reset().
While we're at it drop the test against first_cpu. Setting the compat mode
to the value it already has is redundan
cpu_ppc_set_papr() removes the EP and HV bits from the MSR mask. While
removing the HV bit makes sense (a cpu in PAPR mode should never be
emulated in hypervisor mode), the EP bit is just bizarre. Although it's
true that a papr mode guest shouldn't be able to change the exception
prefix, the MSR[
On Mon, Apr 16, 2018 at 08:44:40AM +0200, Thomas Huth wrote:
> 'vlan' is very confusing since it does not mean something like IEEE
> 802.1Q, but rather emulated hubs, so let's switch to that terminology
> instead.
>
> Buglink: https://bugs.launchpad.net/qemu/+bug/658904
> Signed-off-by: Thomas Hut
Under PAPR, only the boot CPU is active when the system starts. Other cpus
must be explicitly activated using an RTAS call. The entry state for the
boot and secondary cpus isn't identical, but it has some things in common.
We're going to add a bit more common setup later, too, so to simplify
make
There are some fields in the cpu state which need to be updated when the
LPCR register is changed, which is done by ppc_hash64_update_rmls() and
ppc_hash64_update_vrma(). Code which alters env->spr[SPR_LPCR] needs to
call them afterwards to make sure the state is up to date.
That's easy to get wr
On Mon, Apr 16, 2018 at 08:44:39AM +0200, Thomas Huth wrote:
> @@ -499,10 +497,11 @@
> # @opts: device type specific properties (legacy)
> #
> # Since: 1.2
> +#
> +# 'vlan' - removed with 2.12
Not sure how to interpret this. How about "removed in 2.13"?
> @@ -2028,10 +2028,9 @@ DEF("nic", HAS
On Mon, Apr 16, 2018 at 08:44:41AM +0200, Thomas Huth wrote:
> -@subsection Connecting VLANs between QEMU instances
> +@subsection Hubs
> +
> +QEMU can simulate several hubs. A hub can be symbolised as a virtual
> connection
s/symbolised/thought of/
Reviewed-by: Stefan Hajnoczi
signature.asc
> -Original Message-
> From: Kirti Wankhede [mailto:kwankh...@nvidia.com]
> Sent: Monday, April 16, 2018 10:45 PM
> To: Zhang, Yulei ; qemu-devel@nongnu.org
> Cc: Tian, Kevin ; joonas.lahti...@linux.intel.com;
> zhen...@linux.intel.com; Wang, Zhi A ;
> alex.william...@redhat.com; dgilb...
From: Wanpeng Li
This patch adds support for KVM_CAP_X86_DISABLE_EXITS. Provides userspace with
per-VM capability(KVM_CAP_X86_DISABLE_EXITS) to not intercept MWAIT/HLT/PAUSE
in order that to improve latency in some workloads.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Eduardo Habkost
Signed-of
On 17.04.2018 09:21, Stefan Hajnoczi wrote:
> On Mon, Apr 16, 2018 at 08:44:39AM +0200, Thomas Huth wrote:
>> @@ -499,10 +497,11 @@
>> # @opts: device type specific properties (legacy)
>> #
>> # Since: 1.2
>> +#
>> +# 'vlan' - removed with 2.12
>
> Not sure how to interpret this. How about "re
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, April 17, 2018 4:38 AM
> To: Zhang, Yulei
> Cc: qemu-devel@nongnu.org; Tian, Kevin ;
> joonas.lahti...@linux.intel.com; zhen...@linux.intel.com;
> kwankh...@nvidia.com; Wang, Zhi A ;
> dgilb.
On 04/16/2018 07:59 PM, Eduardo Habkost wrote:
> (CCing Zack Cornelius)
>
> On Fri, Apr 13, 2018 at 08:21:26AM +0200, Michal Privoznik wrote:
>> Eduardo et al,
>>
>> I'm looking at 11ae6ed8affdd131e and I wanted to implement libvirt
>> support for that. But more I look at it less I understand it.
From: Wanpeng Li
This patch adds support for KVM_CAP_X86_DISABLE_EXITS. Provides userspace with
per-VM capability(KVM_CAP_X86_DISABLE_EXITS) to not intercept MWAIT/HLT/PAUSE
in order that to improve latency in some workloads.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Eduardo Habkost
Signed-of
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1523952337-27449-1-git-send-email-wanpen...@tencent.com
Subject: [Qemu-devel] [PATCH v2]
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1523952337-27449-1-git-send-email-wanpen...@tencent.com
Subject: [Qemu-devel] [PATCH v2] i386/kvm: add support for
KVM_CAP_X86_DISABLE_EXITS
=== TEST SCRIPT BEGIN ===
#!/bin
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1523953455-28053-1-git-send-email-wanpen...@tencent.com
Subject: [Qemu-devel] [PATCH RESEND v2] i386/kvm: add support for
KVM_CAP_X86_DISABLE_EXITS
=== TEST SCRIPT BEGIN ===
On 16 April 2018 at 20:39, Richard Henderson
wrote:
> On 04/16/2018 03:54 AM, Alex Bennée wrote:
>> +/* Inf / x or 0 / x */
>> +if (a.cls == float_class_inf || a.cls == float_class_zero) {
>> +a.sign = sign;
>> +return a;
>> +}
>
> 0/0 should raise an exception.
It doe
On 16 April 2018 at 14:54, Alex Bennée wrote:
> The re-factoring of div_floats changed the order of checking meaning
> an operation like -inf/0 erroneously raises the divbyzero flag.
> IEEE-754 (2008) specifies this should only occur for operations on
> finite operands.
>
> We fix this by moving t
On 17 April 2018 at 03:53, Richard Henderson
wrote:
> The re-factoring of div_floats changed the order of checking meaning
> an operation like -inf/0 erroneously raises the divbyzero flag.
> IEEE-754 (2008) specifies this should only occur for operations
> on finite operands.
>
> We fix this by mo
Stefan Hajnoczi writes:
> On Mon, Apr 16, 2018 at 05:17:32PM +0800, Peter Xu wrote:
>> On Mon, Apr 16, 2018 at 04:37:48PM +0800, Stefan Hajnoczi wrote:
>> > On Thu, Apr 12, 2018 at 02:11:08PM +0800, Peter Xu wrote:
>> > > In the future the monitor iothread may be accessing the cur_mon as
>> > > w
Hi
On Mon, Apr 16, 2018 at 7:48 PM, Stefan Berger
wrote:
> Recent changes to the CRB code now require that access to locality 0
> be requested before the locality can be used for sending a command.
> This patch adds the request to access the locality.
>
> Signed-off-by: Stefan Berger
> ---
> te
On Tue, Apr 17, 2018 at 11:14:27AM +1000, David Gibson wrote:
> > static void spapr_machine_2_12_class_options(MachineClass *mc)
> > diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
> > index d60b7c6d7a..5e044c44af 100644
> > --- a/include/hw/ppc/spapr.h
> > +++ b/include/hw/ppc/spapr.
On 17/04/2018 10:08, Thomas Huth wrote:
>>> -"-net
>>> nic[,vlan=n][,netdev=nd][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]\n"
>>> +"-net
>>> nic[,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]\n"
>>> "configure or create an on-board (or
On 17 April 2018 at 03:53, Richard Henderson
wrote:
> Without bounding the increment, we can overflow exp either here
> in scalbn_decomposed or when adding the bias in round_canonical.
> This can result in e.g. underflowing to 0 instead of overflowing
> to infinity.
>
> The old softfloat code did
On 16 April 2018 at 17:47, Michael S. Tsirkin wrote:
> The following changes since commit 38e83a71d02e026d4a6d0ab1ef9855c4924c2c68:
>
> Update version for v2.12.0-rc3 release (2018-04-11 19:03:24 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/virt/kvm/mst/q
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, April 17, 2018 4:15 AM
> To: Kirti Wankhede
> Cc: Zhang, Yulei ; qemu-devel@nongnu.org; Tian,
> Kevin ; joonas.lahti...@linux.intel.com;
> zhen...@linux.intel.com; Wang, Zhi A ;
> dgilb...@r
On 04/17/2018 05:08 AM, Marc-André Lureau wrote:
Hi
On Mon, Apr 16, 2018 at 7:48 PM, Stefan Berger
wrote:
Recent changes to the CRB code now require that access to locality 0
be requested before the locality can be used for sending a command.
This patch adds the request to access the locality.
On 12 April 2018 at 08:38, Eric Auger wrote:
> This patch implements the IOMMU Memory Region translate()
> callback. Most of the code relates to the translation
> configuration decoding and check (STE, CD).
>
> Signed-off-by: Eric Auger
> Signed-off-by: Prem Mallappa
> +/* @ssid > 0 not support
On 12 April 2018 at 08:38, Eric Auger wrote:
> At the moment, the SMMUv3 does not support notification on
> TLB invalidation. So let's log an error as soon as such notifier
> gets enabled.
>
> Signed-off-by: Eric Auger
> ---
> hw/arm/smmuv3.c | 11 +++
> 1 file changed, 11 insertions(+)
On 12 April 2018 at 08:38, Eric Auger wrote:
> In case the MSI is translated by an IOMMU we need to fixup the
> MSI route with the translated address.
>
> Signed-off-by: Eric Auger
> Signed-off-by: Bharat Bhushan
>
> ---
> v9 -> v10:
> - use address_space_translate
>
> v5 -> v6:
> - use IOMMUMem
On 16 April 2018 at 17:39, Eduardo Habkost wrote:
> Last remaining fix for -rc4.
>
> The following changes since commit 042f6a31af3d38eefc6ec995cce1d762c41d4515:
>
> Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2018-04-16'
> into staging (2018-04-16 15:30:54 +0100)
>
> are ava
I was able to get the e1000odi DOS driver to correctly detect the Intel
e1000e once I added a PCIe bus, however the e1000 still reports a bad
checksum as of this posting with the master branch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed t
On Mon, 16 Apr 2018 18:17:51 +0100
Peter Maydell wrote:
> On 12 April 2018 at 19:29, Peter Maydell wrote:
> > On 12 April 2018 at 17:40, Igor Mammedov wrote:
> >> if arm_load_kernel() were passed non first_cpu, QEMU would end up
> >> with partially set do_cpu_reset() callback leaving some CPU
On 16 April 2018 at 20:42, Richard Henderson
wrote:
> On 04/16/2018 05:19 AM, Peter Maydell wrote:
>> In commit 8c5931de0ac7738809 we added support for SVE extended
>> sigframe records. These mean that the signal frame might now be
>> larger than the size of the target_rt_sigframe record, so make
Hi
On Mon, Apr 16, 2018 at 9:40 PM, Viktor Prutyanov
wrote:
> This patch adds Windows crashdumping feature. Now QEMU can produce crashdump
> file understandable for WinDbg. The crashdump will be obtained by joining
> physical memory dump and 8K header exposed through vmcoreinfo/fw_cfg device
> by
Eduardo Habkost writes:
> See cover letter for a description of the new test system.
>
> TODO: code clean up
> TODO: write description.
>
> Signed-off-by: Eduardo Habkost
> ---
> scripts/validator.py | 724
> +++
> 1 file changed, 724 insertions(
Thomas Huth writes:
> Many device introspection crashes only happen if you are using a
> certain machine, e.g.:
>
> $ ppc-softmmu/qemu-system-ppc -S -M ref405ep,accel=qtest -qmp stdio
> {"QMP": {"version": {"qemu": {"micro": 50, "minor": 11, "major": 2},
> "package": "build-all"}, "capabilities"
Hi
On Mon, Apr 16, 2018 at 10:57 AM, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
>> Now that we can safely call QOBJECT() on QObject * and children types,
>> we can have a single macro to ref/unref the object.
>>
>> Change the incref/decref prefix name for the more common ref/unref.
>
On Mon, 16 Apr 2018 17:29:23 +0200
Paolo Bonzini wrote:
> On 16/04/2018 16:27, Igor Mammedov wrote:
> > On Mon, 16 Apr 2018 15:30:39 +0200
> > Paolo Bonzini wrote:
> >
> >> On 16/04/2018 15:20, Igor Mammedov wrote:
> >>> Generally object doesn't need to know its own name,
> >>> we use it on
On 12 April 2018 at 08:38, Eric Auger wrote:
> Let's cache config data to avoid fetching and parsing STE/CD
> structures on each translation. We invalidate them on data structure
> invalidation commands.
>
> Signed-off-by: Eric Auger
> ---
> hw/arm/smmu-common.c | 24 +++-
> hw/arm/
On Tue, 17 Apr 2018 14:03:18 +0200
Marc-André Lureau wrote:
> Hi
>
> On Mon, Apr 16, 2018 at 9:40 PM, Viktor Prutyanov
> wrote:
> > This patch adds Windows crashdumping feature. Now QEMU can produce
> > crashdump file understandable for WinDbg. The crashdump will be
> > obtained by joining phys
Hi,
we talked about this the other day, so here are the patches to change
the default cache sizes in qcow2.
Without this patch:
* refcount-cache-size = l2-cache-size / 4
unless otherwise specified by the user. This is wasteful, the refcount
cache is accessed sequentially during normal I/O, so
We have just reduced the refcount cache size to the minimum unless
the user explicitly requests a larger one, so we have to update the
documentation to reflect this change.
Signed-off-by: Alberto Garcia
---
docs/qcow2-cache.txt | 33 -
1 file changed, 16 insertion
Hi
On Tue, Apr 17, 2018 at 2:35 PM, Viktor Prutyanov
wrote:
> On Tue, 17 Apr 2018 14:03:18 +0200
> Marc-André Lureau wrote:
>
>> Hi
>>
>> On Mon, Apr 16, 2018 at 9:40 PM, Viktor Prutyanov
>> wrote:
>> > This patch adds Windows crashdumping feature. Now QEMU can produce
>> > crashdump file under
The L2 and refcount caches have default sizes that can be overridden
using the l2-cache-size and refcount-cache-size (an additional
parameter named cache-size sets the combined size of both caches).
Unless forced by one of the aforementioned parameters, QEMU will set
the unspecified sizes so that
Zhang Chen writes:
> Libvirt or other high level software can use this command query colo status.
> You can test this command like that:
> {'execute':'query-colo-status'}
>
> Signed-off-by: Zhang Chen
> ---
> migration/colo.c| 31 +++
> qapi/migration.json | 33 +
On 16 April 2018 at 19:44, Daniel P. Berrangé wrote:
> On Mon, Apr 16, 2018 at 07:28:28PM +0100, Peter Maydell wrote:
>> On 16 April 2018 at 19:18, Marc-André Lureau
>> wrote:
>> > Commit fb5e19d2e1472e96d72d5e4d89c20033f8ab345c originally fixed the
>> > regression, but was inadvertently broken a
On 17 April 2018 at 13:12, Markus Armbruster wrote:
> Thomas Huth writes:
>> In case someone wants to help with creating some bug fix patches
>> during the QEMU hard freeze phase: This test can now be used to
>> trigger lots of introspection bugs that we were not aware of yet.
>> I think most
On 12 April 2018 at 08:38, Eric Auger wrote:
> We emulate a TLB cache of size SMMU_IOTLB_MAX_SIZE=256.
> It is implemented as a hash table whose key is a combination
> of the 16b asid and 48b IOVA.
>
> Entries are invalidated on TLB invalidation commands, either
> globally, or per asid, or per asi
I'm planning to tag rc4 this afternoon (UK time), which I expect
to be the last rc for the 2.12 series. This is your last chance
to flag up anything we absolutely must fix for this release.
Please reply to this email and also update
https://wiki.qemu.org/Planning/2.12#Known_issues
if there's anythi
Peter Maydell writes:
> On 17 April 2018 at 13:12, Markus Armbruster wrote:
>> Thomas Huth writes:
>>> In case someone wants to help with creating some bug fix patches
>>> during the QEMU hard freeze phase: This test can now be used to
>>> trigger lots of introspection bugs that we were not
Am 17.04.2018 um 15:03 schrieb Peter Maydell:
> I'm planning to tag rc4 this afternoon (UK time), which I expect
> to be the last rc for the 2.12 series. This is your last chance
> to flag up anything we absolutely must fix for this release.
> Please reply to this email and also update
> https://wi
For zynq-7000 boards, we saw issues when u-boot/linux accessing the qspi.
Issue is due to wrong dummy byte transfers for few of un-handled commands ex:
0x9F, 0x6, 0xe9, 0x4, 0x18, etc
There are many unhandled commands which do not require dummy bytes but they can
be followed by address cycles.
T
Hi,
v2:
There is some difference in expected_downtime value due to following
reason,
1. bandwidth and expected_downtime value are calculated in
migration_update_counters() during each iteration from
migration_thread()
2. remaining ram is calculated in qmp_query_migrate() when we actually
call
expected_downtime value is not accurate with dirty_pages_rate * page_size,
using ram_bytes_remaining would yeild it correct.
Signed-off-by: Balamuruhan S
---
migration/migration.c | 6 +++---
migration/migration.h | 1 +
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/migration/mi
Hi
On Mon, Apr 16, 2018 at 10:26 AM, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
>> Following a discussion on the mailing list:
>
> If a reader of this commit message could profit from reading the
> discussion, refer to it by URL and/or Message-Id. If not, don't mention
> it.
>
>>
On 16 April 2018 at 19:44, Henry Wertz wrote:
> Please find submitted a patch for ARM memory barriers. This patch is
> against qemu-2.12-rc2 but I do believe it should apply for anything from
> 2.11.x to current.
Hi Henry; thanks for these patches. Please could you provide
a Signed-off-by: line
By moving the base fields to a QObjectBase_, QObject can be a type
which also has a 'base' field. This allows to write a generic
QOBJECT() macro that will work with any QObject type, including
QObject itself. The container_of() macro ensures that the object to
cast has a QObjectBase_ base field, gi
Hi,
This series aims to get rid of the distinction between QObject, that
must use qobject_incref/qobject_decref and its various derived types
that have to use QINCREF/QDECREF. Instead, replace it with
qobject_ref/qobject_unref for all types.
v5: after Markus review
- various commit message & comm
All QObject types have the base QObject as first field. This allows to
simplify qobject_to() and will allow further simplification in
following patch.
Signed-off-by: Marc-André Lureau
---
include/qapi/qmp/qobject.h | 5 ++---
qobject/qobject.c | 9 +
2 files changed, 11 insertio
For convenience and clarity, make it possible to call qobject_ref() at
the time when the reference is associated with a variable, or
argument, by making qobject_ref() return the same pointer as given.
Signed-off-by: Marc-André Lureau
---
include/qapi/qmp/qnull.h | 3 +--
include/qapi/qmp/q
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, April 17, 2018 4:23 AM
> To: Kirti Wankhede
> Cc: Zhang, Yulei ; qemu-devel@nongnu.org; Tian,
> Kevin ; joonas.lahti...@linux.intel.com;
> zhen...@linux.intel.com; Wang, Zhi A ;
> dgilb...@r
Hi Stefan,
On 04/17/2018 10:19 AM, Stefan Weil wrote:
> Update po files? That's not a "must fix", but it would be nice to have
> those files synchronized with ui/gtk.c again.
Isn't it now fixed by
https://github.com/qemu/qemu/commit/2a6b5372d7bad038fe27f9c60e85ef5c8a15e311
?
Regards,
Phil.
While it may be convenient to accept NULL value in
qobject_unref() (for similar reasons as free() accepts NULL), it is
not such a good idea for qobject_ref(), assert() on NULL. One place
relied on that behaviour (the monitor request id), and it's best to be
explicit that NULL is accepted there.
Si
John Snow writes:
> This series seeks to address two distinct but closely related issues
> concerning the job management API.
>
> (1) For jobs that complete when a monitor is not attached and receiving
> events or notifications, there's no way to discern the job's final
> return code. Job
Forgot to mention: yes, I know this has been merged already. I'm merely
trying to catch up with recent block layer progress.
This patch adds Windows crashdumping feature. Now QEMU can produce ELF-dump
containing Windows crashdump header, which can help to convert to a valid
WinDbg-understandable crashdump file, or immediately create such file.
The crashdump will be obtained by joining physical memory dump and 8K header
e
On 17 April 2018 at 14:19, Stefan Weil wrote:
> Update po files? That's not a "must fix", but it would be nice to have
> those files synchronized with ui/gtk.c again.
Judging by the "POT-Creation-Date" timestamps, we haven't done
that for a year or so, so there doesn't seem to be a great
urgency
+ linux acpi
+qemu-devel
> -Original Message-
> From: Dan Williams [mailto:dan.j.willi...@intel.com]
> Sent: Monday, April 16, 2018 10:23 AM
> To: Schmauss, Erik
> Cc: Zhang, Haozhong ; Moore, Robert
> ; He, Junyan
> Subject: Re: nfit issue
>
> Let's move this discussion on to the maili
> -Original Message-
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Dan Williams
> Sent: Monday, April 16, 2018 4:22 PM
> To: Schmauss, Erik
> Cc: Rafael J. Wysocki ; Linux ACPI a...@vger.kernel.org>; Moore, Robert ; linux-
> nvdimm ; Q
On 17 April 2018 at 14:51, Alex Bennée wrote:
>
> Richard Henderson writes:
>
>> Without bounding the increment, we can overflow exp either here
>> in scalbn_decomposed or when adding the bias in round_canonical.
>> This can result in e.g. underflowing to 0 instead of overflowing
>> to infinity.
Richard Henderson writes:
> Without bounding the increment, we can overflow exp either here
> in scalbn_decomposed or when adding the bias in round_canonical.
> This can result in e.g. underflowing to 0 instead of overflowing
> to infinity.
>
> The old softfloat code did bound the increment.
>
>
Eric Blake writes:
> On 03/12/2018 04:07 AM, Paolo Bonzini wrote:
>> On 12/03/2018 08:27, Thomas Huth wrote:
>>> "-net" is clearly a legacy option. Yet we still use it in almost all
>>> examples in the qemu documentation, and many other spots in the network
>>> chapter. We should make it less pro
ping?
On Tue, Apr 17, 2018 at 03:56:25PM +0200, Markus Armbruster wrote:
> Eric Blake writes:
>
> > On 03/12/2018 04:07 AM, Paolo Bonzini wrote:
> >> On 12/03/2018 08:27, Thomas Huth wrote:
> >>> "-net" is clearly a legacy option. Yet we still use it in almost all
> >>> examples in the qemu documentati
Am 17.04.2018 um 15:50 schrieb Peter Maydell:
> On 17 April 2018 at 14:19, Stefan Weil wrote:
>> Update po files? That's not a "must fix", but it would be nice to have
>> those files synchronized with ui/gtk.c again.
> Judging by the "POT-Creation-Date" timestamps, we haven't done
> that for a yea
This will be used to process IOMMUs in a MemoryRegionCache. This
includes a small bugfix, in that the returned page_mask is now
correctly -1 if the IOMMU memory region maps the entire address
space directly. Previously, address_space_get_iotlb_entry would
return ~TARGET_PAGE_MASK.
Signed-off-by:
MemoryRegionCache was reverted to "normal" address_space_* operations
for 2.9, due to lack of support for IOMMUs. This series reinstates
optimizations, caching only the IOMMU translation but not the IOMMU
lookup and target AddressSpace translation.
Patches 1 to 3 prepare by introducing a new func
Prepare for extracting the IOMMU part to a separate function. Mostly
cosmetic; the only semantic change is that, if there is more than one
cascaded IOMMU and the second one fails to translate, *plen_out is now
adjusted according to the page mask of the first IOMMU.
Signed-off-by: Paolo Bonzini
-
For now, this reduces the text size very slightly due to the newly-added
inlining:
text size before: 9301965
text size after: 9300645
Later, however, the declarations in include/exec/memory_ldst.inc.h will be
reused for the MemoryRegionCache slow path functions.
Signed-off-by: Paolo Bonzin
If the receive window presented to the guest closes, slirp should send a
window update once the window reopens sufficiently, rather than forcing
the guest to send a window probe, which can take several seconds.
Signed-off-by: James Clarke
---
Hi,
I encountered this whilst running a (k)FreeBSD bu
MemoryRegionCache was reverted to "normal" address_space_* operations
for 2.9, due to lack of support for IOMMUs. Reinstate the
optimizations, caching only the IOMMU translation at address_cache_init
but not the IOMMU lookup and target AddressSpace translation are not
cached; now that MemoryRegion
On 17/04/2018 16:05, Daniel P. Berrangé wrote:
>> For what it's worth, my "[RFC PATCH 00/32] Command line QAPIfication"
>> replaces the original parsing art by getopt_long_only().
>>
>> Completing that work will take some time, but once it's done, we can
>> (and I think we should) prefer double-das
Igor Mammedov writes:
[...]
> Series allows to configure NUMA mapping at runtime using QMP
> interface. For that to happen it introduces a new '-preconfig' CLI option
> which allows to pause QEMU before machine_init() is run and
> adds new set-numa-node QMP command which in conjunction with
> que
On Tue, Apr 17, 2018 at 04:05:46PM +0200, Stefan Weil wrote:
> Am 17.04.2018 um 15:50 schrieb Peter Maydell:
> > On 17 April 2018 at 14:19, Stefan Weil wrote:
> >> Update po files? That's not a "must fix", but it would be nice to have
> >> those files synchronized with ui/gtk.c again.
> > Judging
On Fri, Apr 06, 2018 at 10:21:23PM +0100, Igor Druzhinin wrote:
> Commit 99605175c (xen-pt: Fix PCI devices re-attach failed) introduced
> a subtle bug. As soon as the guest switches off Bus Mastering on the
> device it immediately causes all the BARs be unmapped due to the DMA
> address space of t
For zynq-7000 boards, we saw issues when u-boot/linux accessing the qspi.
Issue is due to wrong dummy byte transfers for few of un-handled commands ex:
0x9F, 0x6, 0xe9, 0x4, 0x18, etc
There are many unhandled commands which do not require dummy bytes but they can
be followed by address cycles.
T
Hi
On Tue, Apr 17, 2018 at 3:50 PM, Viktor Prutyanov
wrote:
> This patch adds Windows crashdumping feature. Now QEMU can produce ELF-dump
> containing Windows crashdump header, which can help to convert to a valid
> WinDbg-understandable crashdump file, or immediately create such file.
> The cras
On Tue, Apr 17, 2018 at 04:14:02PM +0200, Paolo Bonzini wrote:
> On 17/04/2018 16:05, Daniel P. Berrangé wrote:
> >> For what it's worth, my "[RFC PATCH 00/32] Command line QAPIfication"
> >> replaces the original parsing art by getopt_long_only().
> >>
> >> Completing that work will take some time
On 17/04/18 15:15, Anthony PERARD wrote:
> On Fri, Apr 06, 2018 at 10:21:23PM +0100, Igor Druzhinin wrote:
>> Commit 99605175c (xen-pt: Fix PCI devices re-attach failed) introduced
>> a subtle bug. As soon as the guest switches off Bus Mastering on the
>> device it immediately causes all the BARs b
On Apr 12 18:17, Peter Maydell wrote:
> On 16 March 2018 at 20:31, Aaron Lindsay wrote:
> > Signed-off-by: Aaron Lindsay
> > ---
> > target/arm/cpu.c | 3 +++
> > target/arm/cpu.h | 1 +
> > 2 files changed, 4 insertions(+)
> >
> > diff --git a/target/arm/cpu.c b/target/arm/cpu.c
> > index b0d03
1 - 100 of 270 matches
Mail list logo
