From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Subject: Re: Xen 4.12 Development Update
Date: Mon, 14 Jan 2019 10:52:43 +0000 [thread overview]
Message-ID: <80e92e13-455a-85d2-6809-4e032dc5ce87@citrix.com> (raw)
In-Reply-To: <20190114101320.31547-1-jgross@suse.com>
On 14/01/2019 10:13, Juergen Gross wrote:
> I have started to include the version number of series associated to each
> feature. Can each owner send an update on the version number if the series
> was posted upstream?
>
> = Projects =
>
> == Hypervisor ==
>
> * Improvements to domain creation (v2)
> - Andrew Cooper
There is not realistically going to be further work done here in the
4.12 timeframe.
The work so far has fixed a load of NULL pointer dereferences for blind
uses of d->vcpu[], but a number still remain for blind uses of
d->vcpu[0]. You can still crash Xen by issuing specific toolstack
hypercalls between createdomain and maxvcpus, but its now far harder
than in 4.11
> === x86 ===
>
> * Fixes to #DB injection
> - Andrew Cooper
Nor this. There is a monitoring interaction issue I haven't got around
to fixing yet, and I've subsequently discovered that the way we inject
debug exceptions on VT-x is broken. There is a specific passage in the
SDM which tells us not to do it the way we do, because otherwise we end
up with incorrect prioritisation of events when resuming the guest.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-01-14 10:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 10:13 Xen 4.12 Development Update Juergen Gross
2019-01-14 10:52 ` Andrew Cooper [this message]
2019-01-14 15:22 ` Lars Kurth
2019-01-14 18:09 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2018-12-17 14:14 Juergen Gross
2018-12-17 14:40 ` Razvan Cojocaru
2018-12-17 18:38 ` Tamas K Lengyel
2018-11-28 10:26 Juergen Gross
2018-11-28 10:36 ` Andrew Cooper
2018-11-28 15:30 ` Christopher Clark
2018-11-29 20:16 ` Volodymyr Babchuk
2018-11-30 5:34 ` Juergen Gross
2018-11-28 10:15 Juergen Gross
2018-11-28 10:19 ` Juergen Gross
2018-11-28 10:27 ` Paul Durrant
2018-11-09 10:16 Juergen Gross
2018-11-09 10:40 ` Wei Liu
2018-11-09 10:53 ` Jan Beulich
2018-11-09 18:02 ` Dario Faggioli
2018-11-09 10:56 ` George Dunlap
2018-11-09 11:07 ` Juergen Gross
2018-11-09 11:32 ` George Dunlap
2018-11-09 11:44 ` Andrew Cooper
2018-11-09 12:05 ` Andrew Cooper
2018-11-09 14:50 ` Julien Grall
2018-10-08 8:44 Juergen Gross
2018-11-28 6:23 ` Chao Gao
2018-09-12 6:54 Juergen Gross
2018-09-12 8:20 ` Jan Beulich
2018-09-12 8:22 ` Paul Durrant
2018-10-02 19:06 ` Wei Liu
[not found] ` <5B98CC5E02000078001E7A00@suse.com>
2018-09-12 8:30 ` Juergen Gross
2018-09-12 8:41 ` Jan Beulich
2018-07-27 16:19 Juergen Gross
2018-07-31 18:19 ` Rich Persaud
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=80e92e13-455a-85d2-6809-4e032dc5ce87@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jgross@suse.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).