All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Saul Wold" <Saul.Wold@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] qemurunner: Add support for qmp commands
Date: Wed, 13 Jan 2021 07:09:36 -0800	[thread overview]
Message-ID: <305572bc-83d8-986a-2e11-367470149930@windriver.com> (raw)
In-Reply-To: <4cde6b73149d57c967f77d213baf3b33e0cfd63b.camel@linuxfoundation.org>



On 1/13/21 3:45 AM, Richard Purdie wrote:
> On Tue, 2021-01-12 at 15:11 -0800, Saul Wold wrote:
>> This adds support for the Qemu Machine Protocol [0] extending
>> the current dump process for Host and Target. The commands are
>> added in the testimage.bbclass.
>>
>> Currently, we setup qemu to stall until qmp gets connected and
>> sends the initialization and continue commands, this works
>> correctly.
>>
>> With this version, the monitor_dumper is created in OEQemuTarget
>> but then set in OESSHTarget as that's where we get the SSH failure
>> happens. Python's @property is used to create a setter/getter type
>> of setup in OESSHTarget to get overridden by OEQemuTarget.
>>
>> By default the data is currently dumped to files for each command in
>> TMPDIR/log/runtime-hostdump/<date>_qmp/unknown_<seq>_qemu_monitor as
>> this is the naming convenstion in the dump.py code.
>>
>> We use the qmp.py from qemu, which needs to get installed in the
>> recipe-sysroot-native of the target image.
>>
>> [0] https://github.com/qemu/qemu/blob/master/docs/interop/qmp-spec.txt
>>
>> Signed-off-by: Saul Wold <saul.wold@windriver.com>
>> ---
>>   meta/classes/testimage.bbclass    |  6 ++++++
>>   meta/lib/oeqa/core/target/qemu.py |  6 ++++++
>>   meta/lib/oeqa/core/target/ssh.py  | 17 +++++++++++++++-
>>   meta/lib/oeqa/targetcontrol.py    |  3 +++
>>   meta/lib/oeqa/utils/dump.py       | 31 +++++++++++++++++++++++++---
>>   meta/lib/oeqa/utils/qemurunner.py | 34 ++++++++++++++++++++++++++++++-
>>   6 files changed, 92 insertions(+), 5 deletions(-)
> 
> For fun I thought I'd try this on the autobuilder:
> 
Seems it was too much fun, looks like I will need to be able to start at 
least one build on the AB.

> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1748
> 
> Looks like we may need to use importlib to import the qmp module as
> otherwise oe-selftest can't launch (and the qmp module may not be
> installed yet).
> 
Ok, I will look into this, it worked correctly for me doing a locally, 
with do_testimage, but clearly I missed something that between the 
qemu-system-native install and the testimage.

> I didn't wade through all the errors, just the oe-selftest one.
> 
I will take a deeper dive on these.

> I also noticed warnings from builds that did work.
>
I will look here also.

Thanks for at least giving it a try.

Sau!


> Cheers,
> 
> Richard
> 

-- 
Sau!

  reply	other threads:[~2021-01-13 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 23:11 [PATCH 0/2] Enable QMP Dumping for testimage Saul Wold
2021-01-12 23:11 ` [PATCH 1/2] qemu-system-native: install qmp python module Saul Wold
2021-01-12 23:11 ` [PATCH 2/2] qemurunner: Add support for qmp commands Saul Wold
2021-01-13 11:45   ` [OE-core] " Richard Purdie
2021-01-13 15:09     ` Saul Wold [this message]
2021-01-13 15:53       ` Richard Purdie
2021-01-12 23:11 ` [PATCH] " Saul Wold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=305572bc-83d8-986a-2e11-367470149930@windriver.com \
    --to=saul.wold@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.