All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Simpson <tsimpson@quicinc.com>
To: Richard Henderson <richard.henderson@linaro.org>,
	Alessandro Di Federico <ale@rev.ng>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: RE: [RFC] Reducing NEED_CPU_H usage
Date: Thu, 2 Mar 2023 17:44:05 +0000	[thread overview]
Message-ID: <SN4PR0201MB880875238DB7B8A8FD531D74DEB29@SN4PR0201MB8808.namprd02.prod.outlook.com> (raw)
In-Reply-To: <e25db9ec-edb2-4dc1-6b7e-3969449f8a8c@linaro.org>



> -----Original Message-----
> From: Richard Henderson <richard.henderson@linaro.org>
> Sent: Saturday, January 14, 2023 6:53 PM
> To: Alessandro Di Federico <ale@rev.ng>
> Cc: qemu-devel@nongnu.org; Taylor Simpson <tsimpson@quicinc.com>;
> Alex Bennée <alex.bennee@linaro.org>
> Subject: Re: [RFC] Reducing NEED_CPU_H usage
> 
> On 1/12/23 05:28, Alessandro Di Federico wrote:
> >      fpu/softfloat.c
> 
> Something I happened to notice while doing other triage:
> 
>      https://gitlab.com/qemu-project/qemu/-/issues/1375
> 
> This is an x86 problem that currently has no solution, but ought to be trivial
> with the changes to softfloat required for this project.

One other thing we'll need to deal with is command-line options.  In a heterogeneous system, options like -cpu and -d will need a way to direct different settings to each target.

Thanks,
Taylor

      reply	other threads:[~2023-03-02 17:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 16:16 [RFC] Reducing NEED_CPU_H usage Alessandro Di Federico via
2022-12-29 19:13 ` Taylor Simpson
2023-01-10 19:56 ` Richard Henderson
2023-01-12 15:28   ` Alessandro Di Federico via
2023-01-12 22:40     ` Richard Henderson
2023-01-15  1:52     ` Richard Henderson
2023-03-02 17:44       ` Taylor Simpson [this message]

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=SN4PR0201MB880875238DB7B8A8FD531D74DEB29@SN4PR0201MB8808.namprd02.prod.outlook.com \
    --to=tsimpson@quicinc.com \
    --cc=ale@rev.ng \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.