From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Joel Stanley <joel@jms.id.au>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Andrew Jeffery" <andrew@aj.id.au>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>, "Cédric Le Goater" <clg@kaod.org>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/2] tests/acceptance: Test ast2400 and ast2500 machines
Date: Thu, 4 Mar 2021 14:29:19 +0100 [thread overview]
Message-ID: <0aae3aa6-1b82-9002-5911-cd5ec8225f72@redhat.com> (raw)
In-Reply-To: <CACPK8XddbgGgPtkK41MM5ZYeaar27RhnD4vQwh8DcXnFpgoUoA@mail.gmail.com>
On 3/3/21 12:19 PM, Joel Stanley wrote:
> On Wed, 3 Mar 2021 at 10:19, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> On 3/3/21 2:22 AM, Joel Stanley wrote:
>>> Test MTD images from the OpenBMC project on AST2400 and AST2500 SoCs
>>> from ASPEED, by booting Palmetto and Romulus BMC machines.
>>>
>>> The images are fetched from OpenBMC's release directory on github.
>>
>> You need to justify here why this is safe to run that
>> on anyone workstation, or use AVOCADO_ALLOW_UNTRUSTED_CODE.
>
> I don't completely understand. What circumstances would it be unsafe
> to run a qemu guest, aside from a bug in qemu itself?
See Alex's rationale here:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg774096.html
Point taken, this should be better documented.
next prev parent reply other threads:[~2021-03-04 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 1:22 [PATCH 0/2] tests/acceptance: Test Aspeed ARM machines Joel Stanley
2021-03-03 1:22 ` [PATCH 1/2] tests/acceptance: Test ast2400 and ast2500 machines Joel Stanley
2021-03-03 7:44 ` Cédric Le Goater
2021-03-03 10:19 ` Philippe Mathieu-Daudé
2021-03-03 11:19 ` Joel Stanley
2021-03-04 13:29 ` Philippe Mathieu-Daudé [this message]
2021-03-03 1:22 ` [PATCH 2/2] tests/acceptance: Test ast2600 machine Joel Stanley
2021-03-03 7:43 ` Cédric Le Goater
2021-03-03 9:32 ` Joel Stanley
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=0aae3aa6-1b82-9002-5911-cd5ec8225f72@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=crosa@redhat.com \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).