From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org, wenchao.wang@intel.com
Subject: Re: [PATCH] docs/about/deprecated: Mark HAXM as deprecated
Date: Wed, 25 Jan 2023 13:31:40 +0100 [thread overview]
Message-ID: <f413e1d6-370c-8552-592e-e58187af9bd5@redhat.com> (raw)
In-Reply-To: <Y9Eb4ZMm0ll4xcM9@redhat.com>
On 25/01/2023 13.09, Daniel P. Berrangé wrote:
> On Wed, Jan 25, 2023 at 11:20:53AM +0100, Thomas Huth wrote:
>> The HAXM project has been retired (see https://github.com/intel/haxm#status),
>> so we should mark the code in QEMU as deprecated (and finally remove it
>> unless somebody else picks the project up again - which is quite unlikely
>> since there are now whpx and hvf on these operating systems, too).
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> docs/about/deprecated.rst | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
>> index 3f4d678eb4..da2e6fe63d 100644
>> --- a/docs/about/deprecated.rst
>> +++ b/docs/about/deprecated.rst
>> @@ -93,6 +93,12 @@ form is preferred.
>> The HPET setting has been turned into a machine property.
>> Use ``-machine hpet=off`` instead.
>>
>> +``-accel hax`` (since 8.0)
>> +''''''''''''''''''''''''''
>> +
>> +The HAXM project has been retired (see https://github.com/intel/haxm#status).
>> +Use "whpx" (on Windows) or "hvf" (on macOS) instead.
>> +
>
> Should we print a warning message from meson when someone enables this ?
Or maybe rather to hax_accel_init() , so that people who run the binary see
the message?
... I can add it there (though I have no means of testing it).
Thomas
prev parent reply other threads:[~2023-01-25 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 10:20 [PATCH] docs/about/deprecated: Mark HAXM as deprecated Thomas Huth
2023-01-25 11:31 ` Philippe Mathieu-Daudé
2023-01-25 12:09 ` Daniel P. Berrangé
2023-01-25 12:31 ` Thomas Huth [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=f413e1d6-370c-8552-592e-e58187af9bd5@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=wenchao.wang@intel.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 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.