From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <ponzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: FR: Patchew Atom Feed for searches
Date: Mon, 07 Mar 2022 17:35:40 +0000 [thread overview]
Message-ID: <87o82hfylv.fsf@linaro.org> (raw)
Something like:
https://patchew.org/QEMU?output=atom
Returns:
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Patchew Patches</title>
<subtitle>for project:QEMU</subtitle>
<link href="http://patchew.org/QEMU?output=atom" rel="self" />
<link href="http://patchew.org/QEMU" />
<id>urn:uuid:60a76c80-d399-11d9-b91C-0003939e0af6</id>
<updated>2003-12-13T18:30:02Z</updated>
<entry>
<title>[RFC PATCH] tests/avocado: update aarch64_virt test to exercise -cpu max</title>
<link href="https://patchew.org/QEMU/20220307172249.3125779-1-alex.bennee@linaro.org/" />
<link rel="alternate" type="text/mbox" href="https://patchew.org/QEMU/20220307172249.3125779-1-alex.bennee@linaro.org/mbox"/>
<id>20220307172249.3125779-1-alex.bennee@linaro.org/</id>
<published>2003-11-09T17:23:02Z</published>
<updated>2003-12-13T18:30:02Z</updated>
<summary>[RFC PATCH] tests/avocado: update aarch64_virt test to exercise -cpu max</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
The Fedora 29 kernel is quite old and importantly fails when running
in LPA2 scenarios. As it's not really exercising much of the CPU space
replace it with a custom 5.16.12 kernel with all the architecture
options turned on. There is a minimal buildroot initramfs included in
the kernel which has a few tools for stress testing the memory
subsystem. The userspace also targets the Neoverse N1 processor so
will fail without additional v8.x+ features.
</div>
</content>
<author>
<name>Alex Bennée</name>
<email>alex.bennee@linaro.org</email>
</author>
</entry>
<entry>
.. and repeat for next entry ..
</entry>
</feed>
--
Alex Bennée
reply other threads:[~2022-03-07 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87o82hfylv.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=ponzini@redhat.com \
--cc=qemu-devel@nongnu.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 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).