From: "Jan Beulich" <JBeulich@suse.com> To: Meng Xu <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com>, Dario Faggioli <firstname.lastname@example.org>, Tianyang Chen <email@example.com>, George Dunlap <firstname.lastname@example.org>, Dagaen Golomb <email@example.com> Subject: Re: [PATCH v11]xen: sched: convert RTDS from time to event driven model Date: Fri, 18 Mar 2016 01:45:20 -0600 [thread overview] Message-ID: <56EBC02002000078000DE324@prv-mh.provo.novell.com> (raw) In-Reply-To: <CAENZ-+=YKbyznj0JH-HyKhHQut3wTN=ZSfLkxFgzeNUbnPm4Tg@mail.gmail.com> >>> On 18.03.16 at 05:09, <firstname.lastname@example.org> wrote: > Great job! However, we still have 1 mile in the 100-mile journey. :-D > > I applied the patch on staging and tried some test cases. One of them > is as follows: > > I tried to create a cpupool and then migrate a VM to the new cpupool; > However, the system triggers the bug as below. I guess this is some > kind of bug that are known to us, and Dario had some uncommitted > patch to fix it, IIRC? In the context of this patch the most relevant question is: Is this an issue with the patch, or one that existed already before? After all that's what we're in need to know whether the change can go in. And skimming over the patch, it doesn't seem to alter code related to where you see things blow up. Jan _______________________________________________ Xen-devel mailing list Xenemail@example.com http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-18 7:45 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-03-17 16:06 Tianyang Chen 2016-03-17 18:27 ` Dario Faggioli 2016-03-17 20:12 ` Chen, Tianyang 2016-03-18 1:45 ` Meng Xu 2016-03-18 4:09 ` Meng Xu 2016-03-18 7:45 ` Jan Beulich [this message] 2016-03-18 9:23 ` Dario Faggioli 2016-03-18 14:23 ` Meng Xu 2016-03-18 14:19 ` Meng Xu 2016-03-18 9:24 ` Dario Faggioli 2016-03-18 14:25 ` Meng Xu
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=56EBC02002000078000DE324@prv-mh.provo.novell.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v11]xen: sched: convert RTDS from time to event driven model' \ /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
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).