From: Jan Beulich <jbeulich@suse.com>
To: pdurrant@amazon.com
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update
Date: Wed, 29 Jan 2020 13:47:37 +0100 [thread overview]
Message-ID: <2de0978b-ad66-47a7-7d9b-07444f955f7a@suse.com> (raw)
In-Reply-To: <20200129123618.1202-1-pdurrant@amazon.com>
On 29.01.2020 13:36, Paul Durrant wrote:
> === x86 ===
>
> * Intel Processor Trace virtualization enabling (v1)
> - Luwei Kang
>
> * Linux stub domains (RFC v2)
> - Marek Marczykowski-Górecki
>
> * Fixes to #DB injection
> - Andrew Cooper
>
> * CPUID/MSR Xen/toolstack improvements
> - Andrew Cooper
>
> * Improvements to domain_crash()
> - Andrew Cooper
>
> * EIBRS
> - Andrew Cooper
>
> * Xen ioreq server (v3)
> - Roger Pau Monne
Do you want to add "x86/HVM: implement memory read caching"
(https://lists.xenproject.org/archives/html/xen-devel/2018-09/msg00976.html)
here? I think I now have something coming a little closer to
what Andrew wants. It has its own downsides, so there being a
v4 (after well over a year) doesn't mean this will get it any
closer to going in.
Do you also want to add the ongoing x86 insn emulator work
here? Some parts were posted, some parts are still in needed
of finding time to carry out, and some parts are still pretty
vague.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-29 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 12:36 [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update Paul Durrant
2020-01-29 12:43 ` Marek Marczykowski-Górecki
2020-01-29 12:57 ` Durrant, Paul
2020-01-29 12:47 ` Jan Beulich [this message]
2020-01-29 13:00 ` Durrant, Paul
2020-01-29 12:59 ` Jürgen Groß
2020-01-29 13:04 ` David Woodhouse
2020-01-29 14:12 ` Tamas K Lengyel
2020-01-29 18:03 ` Andrew Cooper
2020-02-26 10:03 Paul Durrant
2020-03-25 10:19 paul
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=2de0978b-ad66-47a7-7d9b-07444f955f7a@suse.com \
--to=jbeulich@suse.com \
--cc=pdurrant@amazon.com \
--cc=xen-devel@lists.xenproject.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).