From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Cornelia Huck <cohuck@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Victor Kaplansky <victork@redhat.com>
Subject: [Qemu-devel] [PATCH for-2.11 0/2] Improvements for the pxe tester
Date: Wed, 9 Aug 2017 06:59:36 +0200 [thread overview]
Message-ID: <1502254778-14637-1-git-send-email-thuth@redhat.com> (raw)
The first patch improves the buffer handling in the pxe tester a
little bit by allocating a separate buffer on the heap for each
architecture. This also gets rid of the huge pre-initialized
array in the tester, shrinking the size of the executable by
half of a megabyte!
The second patch adds s390x support to the pxe tester. Starting
with QEMU 2.10, the guest firmware on s390x can now net-boot via
TFTP, too, so we can automatically test this code in the pxe tester.
Thomas Huth (2):
tests/boot-sector: Do not overwrite the x86 buffer on other
architectures
tests/pxe: Check virtio-net-ccw on s390x
tests/Makefile.include | 1 +
tests/boot-sector.c | 57 ++++++++++++++++++++++++++++++++++++++------------
tests/pxe-test.c | 7 +++++++
3 files changed, 52 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-08-09 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 4:59 Thomas Huth [this message]
2017-08-09 4:59 ` [Qemu-devel] [PATCH 1/2] tests/boot-sector: Do not overwrite the x86 buffer on other architectures Thomas Huth
2017-08-09 9:05 ` Cornelia Huck
2017-08-09 9:18 ` Thomas Huth
2017-08-09 9:27 ` Cornelia Huck
2017-08-09 4:59 ` [Qemu-devel] [PATCH 2/2] tests/pxe: Check virtio-net-ccw on s390x Thomas Huth
2017-08-09 9:10 ` Cornelia Huck
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=1502254778-14637-1-git-send-email-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=victork@redhat.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).