With the recent addition of the XIVE documentation, we
now have some actual .rST format documentation in
docs/specs, so we should start building and installing
this manual.
Patch 1 in this series fixes up some minor problems with
docs/specs/index.rst which we didn't notice because we
weren't build
The docs/specs/index.rst has a couple of minor issues which
we didn't notice because we weren't building the manual:
* the ToC entry for the new PPC XIVE docs points to
a nonexistent file
* the initial comment needs to be marked by '..', not '.',
or it will appear in the output
* the title
(Sorry for the initial send where I sent only the cover
letter and forgot to tell git send-email to send the
patches as well...)
With the recent addition of the XIVE documentation, we
now have some actual .rST format documentation in
docs/specs, so we should start building and installing
this manu
Now we have some rST format docs in the docs/specs/ manual, we should
actually build and install it.
Signed-off-by: Peter Maydell
---
Makefile | 7 ++-
docs/specs/conf.py | 16
2 files changed, 22 insertions(+), 1 deletion(-)
create mode 100644 docs/specs/conf.py
On 6/10/19 10:02 AM, Andrey Shinkevich wrote:
>
>
> On 10/06/2019 17:24, Eric Blake wrote:
>> On 6/9/19 1:35 PM, Andrey Shinkevich wrote:
>>> With the '-valgrind' option, let all the QEMU processes be run under
>>> the Valgrind tool. The Valgrind own parameters may be set with its
>>> environment
On Tue, Jun 04, 2019 at 03:10:43PM +0800, Like Xu wrote:
> Hi Michael，
>
> At https://www.linux-kvm.org/page/NetworkingTodo, there is an entry for
> network latency saying:
>
> ---
> reduce networking latency:
> allow handling short packets from softirq or VCPU context
> Plan:
>We are going
pull-request' into staging (2019-06-10
> 11:53:19 +0100)
>
> are available in the Git repository at:
>
> https://github.com/rth7680/qemu.git tags/pull-tcg-20190610
>
> for you to fetch changes up to 43b3952dea0f763ceeaa2f119c473b5cc6d29c90:
>
> tcg/arm: Remov
07.06.2019 20:22, Markus Armbruster wrote:
> Vladimir Sementsov-Ogievskiy writes:
>
>> 06.06.2019 14:17, Daniel P. Berrangé wrote:
>>> On Thu, Jun 06, 2019 at 01:15:33PM +0300, Vladimir Sementsov-Ogievskiy
>>> wrote:
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Hi all!
>>
Le 09/06/2019 à 18:43, Lucien Murray-Pitts a écrit :
> Brief overview;
> - Added "CPU class" m68k_feature to each CPU init
> so MOVEC can detect wrong CR (Control Register) access
> - Added cascaded "inheritance" of m68k_features by calling m680xx_cpu_initfn()
> of previous CPU so that 68060 in
On 10/06/19 16:51, l00284672 wrote:
> The pread will hang in attaching disk just when backend storage network
> disconnection .
Would the "open" hang as well in that case?
> I think the locking range of qemu_global_mutex is too large when do qmp
> operation. what
> does the qemu_global_mutex real
It's needed to provide keepalive for nbd client to track server
availability.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
v2: [by Markus's comments]
- improve commit message
- s/keepalive/keep-alive
- update inet_parse()
qapi/sockets.json | 5 -
util/qemu-sockets.c | 22
Am 10.06.19 um 15:52 schrieb Paolo Bonzini:
> On 10/06/19 15:28, Andreas Färber wrote:
>> So if we want a new QMP operation, the most sense would probably make
>> where-can-I-attach-type(foo) returning a list of QOM paths, showing only
>> the first free slot per bus. That would allow a more efficie
On 10/06/19 18:12, Andreas Färber wrote:
> Am 10.06.19 um 15:52 schrieb Paolo Bonzini:
>> On 10/06/19 15:28, Andreas Färber wrote:
>>> So if we want a new QMP operation, the most sense would probably make
>>> where-can-I-attach-type(foo) returning a list of QOM paths, showing only
>>> the first fre
On Mon, Jun 10, 2019 at 09:53:03AM +0100, Daniel P. Berrangé wrote:
> On Fri, Jun 07, 2019 at 03:58:57PM -0300, Eduardo Habkost wrote:
> > CCing Daniel, who wrote commit 6ab3fc32ea64.
> >
> > On Fri, Jun 07, 2019 at 11:44:32AM -0400, Cleber Rosa wrote:
> > > On Fri, Jun 07, 2019 at 12:42:14AM -030
On 10/06/2019 17:24, Peter Maydell wrote:
> The docs/specs/index.rst has a couple of minor issues which
> we didn't notice because we weren't building the manual:
> * the ToC entry for the new PPC XIVE docs points to
>a nonexistent file
> * the initial comment needs to be marked by '..', not
On Mon, Jun 10, 2019 at 02:21:57PM +0100, Peter Maydell wrote:
> On Mon, 10 Jun 2019 at 14:11, Eduardo Habkost wrote:
> >
> > On Mon, Jun 10, 2019 at 01:58:50PM +0100, Peter Maydell wrote:
> > > Hi. This fails to build on one of my buildtest machines:
> > >
> > > ERROR: Cannot use 'python3', Pytho
On Sat, 8 Jun 2019 at 20:29, Richard Henderson
wrote:
>
> On 6/6/19 12:45 PM, Peter Maydell wrote:
> > +n = (a->imm4h << 28) & 0x8000;
> > +i = ((a->imm4h << 4) & 0x70) | a->imm4l;
> > +if (i & 0x40) {
> > +i |= 0x780;
> > +} else {
> > +i |= 0x800;
> > +}
>
On Mon, Jun 10, 2019 at 02:21:57PM +0100, Peter Maydell wrote:
> On Mon, 10 Jun 2019 at 14:11, Eduardo Habkost wrote:
> >
> > On Mon, Jun 10, 2019 at 01:58:50PM +0100, Peter Maydell wrote:
> > > Hi. This fails to build on one of my buildtest machines:
> > >
> > > ERROR: Cannot use 'python3', Pytho
On Mon, 10 Jun 2019 at 18:12, Daniel P. Berrangé wrote:
> There's been two new LTS releases of Ubuntu since then
> with Xenial and Bionic, so IMHO, it is pretty reasonable
> to want to drop Trusty rather than continuing to spend time
> on software versions from 2014 and before. Both our Travis
> a
On Mon, Jun 10, 2019 at 06:15:46PM +0100, Peter Maydell wrote:
> On Mon, 10 Jun 2019 at 18:12, Daniel P. Berrangé wrote:
> > There's been two new LTS releases of Ubuntu since then
> > with Xenial and Bionic, so IMHO, it is pretty reasonable
> > to want to drop Trusty rather than continuing to spen
On Mon, 10 Jun 2019 at 18:30, Daniel P. Berrangé wrote:
> Do you have access to any machine in the compile farm or is access
> granted on a per-machine basis ? If i'm reading this page right:
>
> https://cfarm.tetaneutral.net/machines/list/
>
> there is now one aarch64 machine (gcc117) that is
On Mon, Jun 10, 2019 at 06:38:05PM +0100, Peter Maydell wrote:
> On Mon, 10 Jun 2019 at 18:30, Daniel P. Berrangé wrote:
> > Do you have access to any machine in the compile farm or is access
> > granted on a per-machine basis ? If i'm reading this page right:
> >
> > https://cfarm.tetaneutral
On 2019-06-10 8:19 a.m., Stefan Hajnoczi wrote:
On Sat, Jun 01, 2019 at 08:12:01PM -0400, Gary Dale wrote:
A while back I converted a raw disk image to qcow2 to be able to use
snapshots. However I realize that I may not really understand exactly how
snapshots work. In this particular case, I'm o
On 6/6/19 6:34 PM, Philippe Mathieu-Daudé wrote:
Hi Eddie,
On 6/4/19 12:09 AM, Eddie James wrote:
The XDMA engine embedded in the Aspeed SOCs performs PCI DMA operations
between the SOC (acting as a BMC) and a host processor in a server.
If I got your model correctly, it does no DMA operatio
Public bug reported:
FROM arm32v6/golang:1.10-alpine
docker build -t openhorizon/ibm.gps_arm:2.0.7 -f ./Dockerfile.arm .
Sending build context to Docker daemon 110.6kB
Step 1/12 : FROM arm32v6/golang:1.10-alpine
1.10-alpine: Pulling from arm32v6/golang
05276f4299f2: Pull complete
5657e63df536:
On 6/10/19 10:12 AM, Peter Maydell wrote:
> On Sat, 8 Jun 2019 at 20:29, Richard Henderson
> wrote:
>>
>> On 6/6/19 12:45 PM, Peter Maydell wrote:
>>> +n = (a->imm4h << 28) & 0x8000;
>>> +i = ((a->imm4h << 4) & 0x70) | a->imm4l;
>>> +if (i & 0x40) {
>>> +i |= 0x780;
>>> +
From: "Dr. David Alan Gilbert"
Add the optional interface list to the HMP command.
i.e.
All interfaces
announce_self
Just the named interfaces:
announce_self vn1,vn2
Signed-off-by: Dr. David Alan Gilbert
---
hmp-commands.hx | 6 --
hmp.c | 38 +++
From: "Dr. David Alan Gilbert"
Allow the caller to restrict the set of interfaces that announces are
sent on. The default is still to send on all interfaces.
e.g.
{ "execute": "announce-self", "arguments": { "initial": 50, "max": 550,
"rounds": 5, "step": 50, "interfaces": ["vn2","vn1"] } }
From: "Dr. David Alan Gilbert"
Laine asked for some extra features on the network announce support;
The first allows the announce timer to announce on a subset of the
interfaces.
The second allows there to be multiple timers, each with their own
parameters (including the interface list).
Signe
From: "Dr. David Alan Gilbert"
Previously there was a single instance of the timer used by
monitor triggered announces, that's OK, but when combined with the
previous change that lets you have announces for subsets of interfaces
it's a bit restrictive if you want to do different things to differe
From: "Dr. David Alan Gilbert"
Add the optional ID to the HMP command.
e.g.
# start an announce for a long time on eth1
migrate_set_parameter announce-rounds 1000
announce_self "eth1" e1
# start an announce on eth2
announce_self "eth2" e2
# Change e1 to be announcing on eth1
On Mon, Jun 10 2019 at 5:07am -0400,
Pankaj Gupta wrote:
> This patch sets dax device 'DAXDEV_SYNC' flag if all the target
> devices of device mapper support synchrononous DAX. If device
> mapper consists of both synchronous and asynchronous dax devices,
> we don't set 'DAXDEV_SYNC' flag.
>
On 06/07/2019 12:22 PM, Cleber Rosa wrote:
Because Travis doesn't allow us to keep files produced during tests
(such as log files), let's print the complete job log to the "console"
in case of job failures.
This is a debugging aid, and given that there's been some timeouts
happening on some te
On 6/10/19 1:43 PM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Allow the caller to restrict the set of interfaces that announces are
> sent on. The default is still to send on all interfaces.
>
> e.g.
>
> { "execute": "announce-self", "arguments": { "initial": 5
From: Aleksandar Markovic
Rather than optputing a cryptic message:
FAIL: True not found in [False],
the following will be reported too, if the command output does not meet
specified expectations:
'lspci -d 11ab:4620' output doesn't contain the word 'GT-64120'
Signed-off-by: Aleksandar Markovi
On 06/07/2019 12:22 PM, Cleber Rosa wrote:
It's a good practice (I'd really say a must) to pin as much as
possible of the software versions used during test, so let's apply
that to paramiko.
According to https://pypi.org/project/paramiko/, 2.4.2 is the latest
released version. It's also easil
On 06/07/2019 12:22 PM, Cleber Rosa wrote:
Commit 9531d26c10 removed all of ":avocado: enable" tags, but then
a new entry was added with the introduction of migration.py.
Let's remove it for consistency.
Signed-off-by: Cleber Rosa
---
tests/acceptance/migration.py | 3 ---
1 file changed,
Hi Cleber,
On 06/07/2019 12:22 PM, Cleber Rosa wrote:
Just like the previous tests, boots a Linux kernel on a ppc64 target
using the pseries machine.
Signed-off-by: Cleber Rosa
Reviewed-by: Caio Carrara
CC: Daniel P. Berrangé
---
.travis.yml| 2 +-
tests/accep
On 6/10/19 1:44 PM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Previously there was a single instance of the timer used by
> monitor triggered announces, that's OK, but when combined with the
> previous change that lets you have announces for subsets of interfaces
>
On 6/6/19 12:30 PM, Michael Rolnik wrote:
> +target_long cpc;
> +target_long npc;
CPC gets copied back and forth to NPC, but is now otherwise unused.
You can drop that.
> +static void translate(DisasContext *ctx)
> +{
> +uint32_t opcode;
> +int res;
> +/* PC points to words.
On 06/07/2019 12:22 PM, Cleber Rosa wrote:
While running in parallel, the VNC tests that use a TCP port easily
collide. There's a number of possibilities to reduce the probability
of collisions, but none that completely prevents it from happening.
So, to avoid those collisions, and given that
On 06/07/2019 12:22 PM, Cleber Rosa wrote:
The test name is composed of the class name and method name, so it
looks like there's some redundancy here that we can eliminate.
Signed-off-by: Cleber Rosa
---
tests/acceptance/vnc.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Revi
On 6/6/19 12:30 PM, Michael Rolnik wrote:
> +enum {
> +BS_NONE = 0, /* Nothing special (none of the below) */
> +BS_STOP = 1, /* We want to stop translation for any reason */
> +BS_BRANCH = 2, /* A branch condition is reached */
> +BS_EXCP = 3, /* An exception condition is reached *
On 06/07/2019 12:22 PM, Cleber Rosa wrote:
This goes a bit further than the other tests, and does a basic (read
only) interaction with the VNC protocol.
This is not a enough to perform a handshake, but enough to make sure
that the socket is somewhat operational and that the expected initial
st
On 6/6/19 12:30 PM, Michael Rolnik wrote:
> +if ((ctx.cpc & (TARGET_PAGE_SIZE - 1)) == 0) {
> +break; /* page boundary */
> +}
This test isn't right, because this ended the TB if the *first* instruction was
located on the page boundary. It also fails to allow for a 32-
From: Adriana Kobylak
The Swift board is an OpenPOWER system hosting POWER processors.
Add support for their BMC including the I2C devices as found on HW.
Signed-off-by: Adriana Kobylak
Reviewed-by: Cédric Le Goater
---
hw/arm/aspeed.c | 50 ++
Hi Eduardo,
On 06/07/2019 06:15 PM, Eduardo Habkost wrote:
It will help us debug issues when tests fail.
Signed-off-by: Eduardo Habkost
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 75e017a5cf..82c74673e1 100644
--- a/.tr
On 6/6/19 12:30 PM, Michael Rolnik wrote:
> +if (ctx.check_skip > 0) {
> +TCGLabel *skip = gen_new_label();
> +TCGLabel *done = gen_new_label();
> +
> +tcg_gen_brcondi_tl(TCG_COND_NE, cpu_skip, 0, skip);
> +translate(&ctx);
> +
On 2019-06-10 11:54 a.m., Gary Dale wrote:
On 2019-06-10 8:19 a.m., Stefan Hajnoczi wrote:
On Sat, Jun 01, 2019 at 08:12:01PM -0400, Gary Dale wrote:
A while back I converted a raw disk image to qcow2 to be able to use
snapshots. However I realize that I may not really understand
exactly how
s
On Jun 10, 2019 5:25 PM, "Peter Maydell" wrote:
>
> Now we have some rST format docs in the docs/specs/ manual, we should
> actually build and install it.
>
> Signed-off-by: Peter Maydell
> ---
Acked-by: Aleksandar Markovic
> Makefile | 7 ++-
> docs/specs/conf.py | 16
On Jun 10, 2019 5:25 PM, "Peter Maydell" wrote:
>
> The docs/specs/index.rst has a couple of minor issues which
> we didn't notice because we weren't building the manual:
> * the ToC entry for the new PPC XIVE docs points to
>a nonexistent file
> * the initial comment needs to be marked by '
On 6/10/19 10:54 AM, Gary Dale wrote:
>>> One explanation I've seen of the process is if I delete a snapshot, the
>>> changes it contains are merged with its immediate child.
>> Nope. Deleting a snapshot decrements the reference count on all its
>> data clusters. If a data cluster's reference co
On 6/10/19 4:27 PM, Gary Dale wrote:
>>
> Trying this against a test VM, I ran into a roadblock. My command line
> and the results are:
>
> # virsh blockcommit stretch "/home/secure/virtual/stretch.qcow2" --top
> stretchS3 --delete --wait
> error: unsupported flags (0x2) in function qemuDomainBlo
On 2019-06-10 6:04 p.m., Eric Blake wrote:
On 6/10/19 10:54 AM, Gary Dale wrote:
One explanation I've seen of the process is if I delete a snapshot, the
changes it contains are merged with its immediate child.
Nope. Deleting a snapshot decrements the reference count on all its
data clusters.
On 6/10/19 5:47 PM, Gary Dale wrote:
>>>
>>> Since blockcommit would make it impossible for me to revert to an
>>> earlier state (because I'm committing the oldest snapshot, if it screws
>>> up, I can't undo within virsh), I need to make sure this command is
>>> correct.
>>>
>>>
> Interesting. You
On 2019-06-10 6:07 p.m., Eric Blake wrote:
On 6/10/19 4:27 PM, Gary Dale wrote:
Trying this against a test VM, I ran into a roadblock. My command line
and the results are:
# virsh blockcommit stretch "/home/secure/virtual/stretch.qcow2" --top
stretchS3 --delete --wait
error: unsupported flags
On Mon, Jun 10, 2019 at 09:49:10PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Rather than optputing a cryptic message:
>
> FAIL: True not found in [False],
>
> the following will be reported too, if the command output does not meet
> specified expectations:
>
> 'lspci -d
On 6/10/19 6:00 PM, Gary Dale wrote:
>>> Any ideas on what I'm doing wrong?
>> Do you know for sure whether you have internal or external snapshots?
>> And at this point, your questions are starting to wander more into
>> libvirt territory.
>>
> Yes. I'm using internal snapshots. From your other e
Public bug reported:
vm guest is linux, executed with tcg
running this Node.js snippet leads to
$ node
> a = undefined
undefined
> a >>> 0
4294967295
host node
$ node
> a = undefined
undefined
> a >>> 0
0
same with |=
node
Welcome to Node.js v12.4.0.
Type ".help" for more information.
> let bu
-- Would the "open" hang as well in that case?
The "open" doesn't hang in that case.
Do you have any better solutions to solve this problem in the case?
On 2019/6/11 0:03, Paolo Bonzini wrote:
On 10/06/19 16:51, l00284672 wrote:
The pread will hang in attaching disk just when backend s
On Fri, Jun 07, 2019 at 09:28:49AM -0500, Richard Henderson wrote:
> On 6/7/19 9:09 AM, Laurent Vivier wrote:
> > On 07/06/2019 11:29, Laurent Vivier wrote:
> >> On 29/05/2019 08:49, David Gibson wrote:
> >>> From: Richard Henderson
> >>>
> >>> The gvec expanders take care of masking the shift amo
On 2019-06-10 8:10 p.m., Eric Blake wrote:
On 6/10/19 6:00 PM, Gary Dale wrote:
Any ideas on what I'm doing wrong?
Do you know for sure whether you have internal or external snapshots?
And at this point, your questions are starting to wander more into
libvirt territory.
Yes. I'm using intern
On Jun 11, 2019 1:24 AM, "Cleber Rosa" wrote:
>
> On Mon, Jun 10, 2019 at 09:49:10PM +0200, Aleksandar Markovic wrote:
> > From: Aleksandar Markovic
> >
> > Rather than optputing a cryptic message:
> >
> > FAIL: True not found in [False],
> >
> > the following will be reported too, if the command
Hello Adriana,
On 10/06/2019 22:53, Adriana Kobylak wrote:
> From: Adriana Kobylak
>
> The Swift board is an OpenPOWER system hosting POWER processors.
> Add support for their BMC including the I2C devices as found on HW.
>
> Signed-off-by: Adriana Kobylak
> Reviewed-by: Cédric Le Goater
I
On Fri, Jun 07, 2019 at 05:03:42PM -0700, Palmer Dabbelt wrote:
> On Thu, 06 Jun 2019 16:22:47 PDT (-0700), alistai...@gmail.com wrote:
> > Hello,
> >
> > As a test of the waters, how would the QEMU community feel about
> > including the RISC-V OpenSBI project as a ROM submodule?
> >
> > The idea
The VIRTIO_NET_F_CTRL_VLAN feature requires the support of
vhost-user backend. But it will be advertised to guest driver
as long as it's enabled by users in QEMU, while it's not
supported by vhost-user backend. This patch fixes this issue.
Fixes: 72018d1e1917 ("vhost-user: ignore qemu-only feature
On 06/06/2019 23:42, Eddie James wrote:
>
> On 6/6/19 1:16 AM, Cédric Le Goater wrote:
>> Hello Eddie,
>>
>> On 04/06/2019 00:09, Eddie James wrote:
>>> The XDMA engine embedded in the Aspeed SOCs performs PCI DMA operations
>>> between the SOC (acting as a BMC) and a host processor in a server.
>
101 - 168 of 168 matches
Mail list logo
