qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: josh@joshtriplett.org
To: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Tsirkin <mtsirkin@redhat.com>,
	edk2-devel-01 <edk2-devel@ml01.01.org>,
	Shannon Zhao <zhaoshenglong@huawei.com>,
	qemu devel list <qemu-devel@nongnu.org>,
	"Moore, Robert" <robert.moore@intel.com>,
	"Smith, Jonathan D" <jonathan.d.smith@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>, Jake Edge <jake@lwn.net>
Subject: Re: [Qemu-devel] "Using Python to investigate EFI and ACPI"
Date: Thu, 3 Sep 2015 08:22:54 -0700	[thread overview]
Message-ID: <20150903152254.GA22612@cloud> (raw)
In-Reply-To: <20150903145007.GA5145@x>

On Thu, Sep 03, 2015 at 07:50:07AM -0700, Josh Triplett wrote:
> On Thu, Sep 03, 2015 at 11:16:40AM +0200, Laszlo Ersek wrote:
> > I'm excited because for virtualization we might have the reverse use
> > case: use BITS to test / debug / develop the ACPI generator of QEMU. :)
> 
> Awesome.  Unit testing and CI for QEMU sounds like an ideal use case for
> BITS.
[...]
> > But, for simple testing, can we maybe run your tool within the guest,
> > before the runtime OS boots?
> 
> Yes, absolutely.  We have a batch-mode testing mechanism based on a
> config file; you'd probably want to make use of that.  With some
> extensions, it could dump results either to an emulated serial port or
> some other interface that you can read from outside qemu.  We also need
> to work on making the results more machine-parseable for automation.

One other note on that front: if you write new tests for ACPI (see
python/testacpi.py), or new data structure parsers, please feel free to
contribute them back to BITS, and we'll happily run them on non-qemu
systems as well.

- Josh Triplett

  reply	other threads:[~2015-09-03 15:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  9:16 [Qemu-devel] "Using Python to investigate EFI and ACPI" Laszlo Ersek
2015-09-03  9:41 ` Laszlo Ersek
2015-09-03 14:48   ` Jake Edge
2015-09-03 14:50 ` Josh Triplett
2015-09-03 15:22   ` josh [this message]
2015-09-03 15:53   ` Laszlo Ersek
2015-09-03 15:57     ` Moore, Robert
2015-09-03 16:16       ` Laszlo Ersek
2015-09-03 16:19         ` Moore, Robert
2015-09-03 16:41     ` josh
2015-09-03 17:19       ` Laszlo Ersek
2015-09-03 21:25         ` josh
2015-09-03 23:21           ` Laszlo Ersek
2015-09-04 17:11             ` josh

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=20150903152254.GA22612@cloud \
    --to=josh@joshtriplett.org \
    --cc=edk2-devel@ml01.01.org \
    --cc=imammedo@redhat.com \
    --cc=jake@lwn.net \
    --cc=jonathan.d.smith@intel.com \
    --cc=lersek@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mtsirkin@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.moore@intel.com \
    --cc=zhaoshenglong@huawei.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).