From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>
Cc: Kevin <kevin.tian@intel.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
AndrewCooper <andrew.cooper3@citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
Yong Y Wang <yong.y.wang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Requesting for freeze exception for RMRR
Date: Fri, 17 Jul 2015 22:33:57 +0800 [thread overview]
Message-ID: <55A91255.1010901@intel.com> (raw)
In-Reply-To: <20150717140157.GM12455@zion.uk.xensource.com>
>> My main disagreement here continues to be that we're talking
>> about a bug fix, and hence I don't view this as needing a freeze
>> exception in the first place (at least not at this point in time). Yes,
>> the bug fix involves adding code that looks like a new feature, but
>> that happens with bug fixes.
>>
>
> Fine then. I'm not going to argue feature vs bug fix at this stage. The
> final resolution is still the same. Tiejun can continue working on this
> next week.
>
Wei and Jan,
Really thanks for your clarification to this case.
Looks two key problems should be addressed as follows:
#1. mmio conflicting with RDM
As Jan suggested George's patch is fine in this phrase.
#2. construct e820
I need to understand what Jan comments properly than resend a patch.
I'm going to finalize these things next week as early as possible.
Again, thanks for all guys's help and I can't walk here without any your
guides.
Thanks
Tiejun
next prev parent reply other threads:[~2015-07-17 14:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 6:31 Requesting for freeze exception for RMRR Chen, Tiejun
2015-07-13 8:11 ` Jan Beulich
2015-07-13 11:41 ` Wei Liu
2015-07-14 1:27 ` Chen, Tiejun
2015-07-14 9:29 ` Wei Liu
2015-07-17 1:16 ` Chen, Tiejun
2015-07-17 9:17 ` Wei Liu
2015-07-17 9:24 ` Chen, Tiejun
2015-07-17 9:30 ` Wei Liu
2015-07-17 13:21 ` Wei Liu
2015-07-17 13:43 ` Jan Beulich
2015-07-17 14:01 ` Wei Liu
2015-07-17 14:33 ` Chen, Tiejun [this message]
2015-07-17 15:11 ` Andrew Cooper
2015-07-17 15:26 ` Chen, Tiejun
2015-07-17 15:32 ` Wei Liu
2015-07-17 15:37 ` Chen, Tiejun
2015-07-20 1:14 ` Tian, Kevin
2015-07-13 13:38 ` Jan Beulich
2015-07-14 0:26 ` Chen, Tiejun
2015-07-14 9:18 ` Jan Beulich
2015-07-14 9:25 ` Ian Campbell
2015-07-14 9:36 ` Jan Beulich
2015-07-14 9:27 ` Chen, Tiejun
2015-07-14 9:38 ` Jan Beulich
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=55A91255.1010901@intel.com \
--to=tiejun.chen@intel.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yong.y.wang@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 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).