xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 9 Nov 2018 12:05:21 +0000	[thread overview]
Message-ID: <ce2cdceb-b2ab-264c-6891-b540ec0521d2@citrix.com> (raw)
In-Reply-To: <e6bb3662-998e-4d9e-cec1-25a33b81a593@citrix.com>

On 09/11/18 11:44, Andrew Cooper wrote:
> On 09/11/18 10:16, Juergen Gross wrote:
>> = Projects =
>>
>> == Hypervisor == 
>>
>> *  Improvements to domain creation (v2)
>>   -  Andrew Cooper
> There is one known bug which definitely needs resolving before 4.12 goes
> out.  Attempting to create a VM with 0 vcpus trips over a bad error path
> when we try to remove permissions for an irq which we never gave in the
> first place.  The fix is most likely to not change irq permissions on unmap.
>
> Beyond that, the next actions are to make the create/destroy paths
> idempotent.  If anyone feels like helping out here, please do.
>
> After that, DOMCTL_max_vcpus needs to be folded into the create path.
>
> An orthogonal task, which really also needs doing before 4.12 goes out
> is to rearrange the point at which d->max_cpus is calculated, so ARM
> gets this number early enough in construction to properly build the
> GIC.  (At the moment, there is a bait-and-switch to defer GIC
> construction until the first vcpu is being constructed).

Oh - another one I forgot.

* Improvements to domain_crash()

The purpose of this is to fix a livepatching bug, but it has the side
effect of fixing the fact that in release builds, most domain_crash()'s
have no clarifying information as to what went wrong.

I've posted about half the work.  What remains in the monolithic patch
to change domain_crash()'s API to make it printk-like.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-11-09 12:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 10:16 Xen 4.12 Development Update 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 [this message]
2018-11-09 14:50 ` Julien Grall
  -- strict thread matches above, loose matches on Subject: below --
2019-01-14 10:13 Juergen Gross
2019-01-14 10:52 ` Andrew Cooper
2019-01-14 15:22 ` Lars Kurth
2019-01-14 18:09   ` Stefano Stabellini
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-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=ce2cdceb-b2ab-264c-6891-b540ec0521d2@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).