From: Ian Campbell <Ian.Campbell@citrix.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"tim@xen.org" <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>,
"Chen, Tiejun" <tiejun.chen@intel.com>
Subject: Re: (v2) Design proposal for RMRR fix
Date: Mon, 12 Jan 2015 12:23:12 +0000 [thread overview]
Message-ID: <1421065392.26317.21.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZYN+dTg7OHrJwUi+_=K7rEGhZU6UScp9dRLN1zyfb41aA@mail.gmail.com>
On Mon, 2015-01-12 at 12:13 +0000, George Dunlap wrote:
> On Mon, Jan 12, 2015 at 11:22 AM, Tian, Kevin <kevin.tian@intel.com> wrote:
> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> Sent: Monday, January 12, 2015 6:23 PM
> >>
> >> >>> On 12.01.15 at 11:12, <kevin.tian@intel.com> wrote:
> >> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> >> Sent: Monday, January 12, 2015 6:09 PM
> >> >>
> >> >> >>> On 12.01.15 at 10:56, <kevin.tian@intel.com> wrote:
> >> >> > the result is related to another open whether we want to block guest
> >> >> > boot for such problem. If 'warn' in domain builder is acceptable, we
> >> >> > don't need to change lowmem for such rare 1GB case, just throws
> >> >> > a warning for unnecessary conflictions (doesn't hurt if user doesn't
> >> >> > assign it).
> >> >>
> >> >> And how would you then deal with the one guest needing that
> >> >> range reserved?
> >> >
> >> > if guest needs the range, then report-all or report-sel doesn't matter.
> >> > domain builder throws the warning, and later device assignment will
> >> > fail (or warn w/ override). In reality I think 1GB is rare. Making such
> >> > assumption to simplify implementation is reasonable.
> >>
> >> One of my main problems with all you recent argumentation here
> >> is the arbitrary use of the 1Gb boundary - there's nothing special
> >> in this discussion with where the boundary is. Everything revolves
> >> around the (undue) effect of report-all on domains not needing all
> >> of the ranges found on the host.
> >>
> >
> > I'm not sure which part of my argument is not clear here. report-all
> > would be a problem here only if we want to fix all the conflictions
> > (then pulling unnecessary devices increases the confliction possibility)
> > in the domain builder. but if we only fix reasonable ones (e.g. >3GB)
> > while warn other conflictions (e.g. <3G) in domain builder (let later
> > assignment path to actually fail if confliction does matter), then we
> > don't need to solve all conflictions in domain builder (if say 1G example
> > fixing it may instead reduce lowmem greatly) and then report-all
> > may just add more warnings than report-sel for unused devices.
>
> You keep saying "report-all" or "report-sel", but I'm not 100% clear
> what you mean by those.
Is the distinction between "all reserved areas" and "only (selectively)
those which are related to an RMRR"? That's how I've been reading it...
Ian.
next prev parent reply other threads:[~2015-01-12 12:23 UTC|newest]
Thread overview: 139+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 11:23 (v2) Design proposal for RMRR fix Tian, Kevin
2015-01-08 0:43 ` Tian, Kevin
2015-01-08 12:32 ` Tim Deegan
2015-01-09 0:53 ` Tian, Kevin
2015-01-09 12:00 ` Andrew Cooper
2015-01-08 12:49 ` George Dunlap
2015-01-08 12:54 ` George Dunlap
2015-01-08 13:00 ` Jan Beulich
2015-01-08 15:15 ` George Dunlap
2015-01-08 15:21 ` Jan Beulich
2015-01-09 2:43 ` Tian, Kevin
2015-01-12 11:25 ` George Dunlap
2015-01-12 13:56 ` Pasi Kärkkäinen
2015-01-12 14:23 ` George Dunlap
2015-01-08 12:58 ` Jan Beulich
2015-01-09 2:29 ` Tian, Kevin
2015-01-09 9:24 ` Jan Beulich
2015-01-09 10:03 ` Tian, Kevin
2015-01-09 2:42 ` Tian, Kevin
2015-01-08 13:54 ` Jan Beulich
2015-01-08 15:59 ` George Dunlap
2015-01-08 16:10 ` Jan Beulich
2015-01-08 18:02 ` George Dunlap
2015-01-08 18:12 ` Pasi Kärkkäinen
2015-01-09 3:12 ` Tian, Kevin
2015-01-09 8:58 ` Jan Beulich
2015-01-09 20:27 ` Konrad Rzeszutek Wilk
2015-01-12 9:44 ` Tian, Kevin
2015-01-12 12:12 ` Ian Campbell
2015-01-14 20:06 ` Konrad Rzeszutek Wilk
2015-01-09 2:49 ` Tian, Kevin
2015-01-09 2:27 ` Tian, Kevin
2015-01-09 9:21 ` Jan Beulich
2015-01-09 10:10 ` Tian, Kevin
2015-01-09 10:35 ` Jan Beulich
2015-01-12 8:46 ` Tian, Kevin
2015-01-12 9:32 ` Jan Beulich
2015-01-12 9:41 ` Tian, Kevin
2015-01-12 9:50 ` Jan Beulich
2015-01-12 9:56 ` Tian, Kevin
2015-01-12 10:08 ` Jan Beulich
2015-01-12 10:12 ` Tian, Kevin
2015-01-12 10:22 ` Jan Beulich
2015-01-12 11:22 ` Tian, Kevin
2015-01-12 11:37 ` Jan Beulich
2015-01-12 11:41 ` Tian, Kevin
2015-01-12 12:03 ` Jan Beulich
2015-01-12 12:16 ` Tian, Kevin
2015-01-12 12:46 ` Jan Beulich
2015-01-12 12:13 ` George Dunlap
2015-01-12 12:23 ` Ian Campbell [this message]
2015-01-12 12:28 ` Tian, Kevin
2015-01-12 14:19 ` George Dunlap
2015-01-13 11:03 ` Tian, Kevin
2015-01-13 11:56 ` Jan Beulich
2015-01-13 12:03 ` Tian, Kevin
2015-01-13 15:52 ` Jan Beulich
2015-01-13 15:58 ` George Dunlap
2015-01-14 8:06 ` Tian, Kevin
2015-01-14 9:00 ` Jan Beulich
2015-01-14 9:43 ` Tian, Kevin
2015-01-14 10:24 ` Jan Beulich
2015-01-14 12:01 ` George Dunlap
2015-01-14 12:11 ` Tian, Kevin
2015-01-14 14:32 ` Jan Beulich
2015-01-14 14:37 ` George Dunlap
2015-01-14 14:47 ` Jan Beulich
2015-01-14 18:29 ` George Dunlap
2015-01-15 8:37 ` Jan Beulich
2015-01-15 9:36 ` Tian, Kevin
2015-01-15 10:06 ` Jan Beulich
2015-01-18 8:36 ` Tian, Kevin
2015-01-19 8:42 ` Jan Beulich
2015-01-15 11:45 ` George Dunlap
2015-01-18 8:58 ` Tian, Kevin
2015-01-19 9:32 ` Jan Beulich
2015-01-19 11:24 ` Tian, Kevin
2015-01-19 11:33 ` Tim Deegan
2015-01-19 11:41 ` Jan Beulich
2015-01-19 12:23 ` Tim Deegan
2015-01-19 13:00 ` George Dunlap
2015-01-20 0:52 ` Tian, Kevin
2015-01-20 8:43 ` Jan Beulich
2015-01-20 8:56 ` Tian, Kevin
2015-01-20 12:56 ` George Dunlap
2015-01-21 2:43 ` Tian, Kevin
2015-01-19 13:52 ` Jan Beulich
2015-01-19 15:29 ` Tim Deegan
2015-01-20 0:45 ` Tian, Kevin
2015-01-20 7:29 ` Jan Beulich
2015-01-20 8:59 ` Tian, Kevin
2015-01-20 9:10 ` Jan Beulich
2015-01-20 10:38 ` Ian Campbell
2015-01-20 10:48 ` Jan Beulich
2015-01-21 2:30 ` Tian, Kevin
2015-01-21 10:18 ` Jan Beulich
2015-01-19 10:21 ` George Dunlap
2015-01-19 11:08 ` Ian Campbell
2015-01-14 12:03 ` Tian, Kevin
2015-01-14 14:34 ` Jan Beulich
2015-01-14 12:12 ` George Dunlap
2015-01-14 14:36 ` Jan Beulich
2015-01-14 12:16 ` George Dunlap
2015-01-14 14:39 ` Jan Beulich
2015-01-14 18:16 ` George Dunlap
2015-01-14 12:21 ` Ian Campbell
2015-01-14 12:17 ` Ian Campbell
2015-01-14 15:07 ` Jan Beulich
2015-01-14 15:18 ` Ian Campbell
2015-01-14 15:39 ` George Dunlap
2015-01-14 15:43 ` Ian Campbell
2015-01-14 18:14 ` George Dunlap
2015-01-15 10:05 ` Ian Campbell
2015-01-15 11:58 ` George Dunlap
2015-01-14 16:26 ` Jan Beulich
2015-01-15 8:40 ` Tian, Kevin
2015-01-14 12:29 ` George Dunlap
2015-01-14 14:42 ` Jan Beulich
2015-01-14 18:22 ` George Dunlap
2015-01-15 8:18 ` Tian, Kevin
2015-01-13 13:45 ` George Dunlap
2015-01-13 15:47 ` Jan Beulich
2015-01-13 16:00 ` George Dunlap
2015-01-13 16:06 ` Jan Beulich
2015-01-14 6:52 ` Tian, Kevin
2015-01-14 12:14 ` Ian Campbell
2015-01-14 12:23 ` George Dunlap
2015-01-15 8:12 ` Tian, Kevin
2015-01-13 16:45 ` Konrad Rzeszutek Wilk
2015-01-14 8:13 ` Tian, Kevin
2015-01-14 9:02 ` Jan Beulich
2015-01-14 9:44 ` Tian, Kevin
2015-01-14 10:25 ` Jan Beulich
2015-01-14 20:42 ` Konrad Rzeszutek Wilk
2015-01-15 8:09 ` Tian, Kevin
2015-01-16 17:17 ` Konrad Rzeszutek Wilk
2015-01-15 8:43 ` Jan Beulich
2015-01-14 12:47 ` George Dunlap
2015-01-12 12:30 ` Tian, Kevin
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=1421065392.26317.21.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dunlapg@umich.edu \
--cc=ian.jackson@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tiejun.chen@intel.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@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.