xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Kevin <kevin.tian@intel.com>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
	"Wang, Yong Y" <yong.y.wang@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: Requesting for freeze exception for RMRR
Date: Fri, 17 Jul 2015 17:24:55 +0800	[thread overview]
Message-ID: <55A8C9E7.7080702@intel.com> (raw)
In-Reply-To: <20150717091726.GG12455@zion.uk.xensource.com>

>> * On hvmloader side, there three patches now:
>>    patch #5 is reviewed by George and Acked by Jan;
>>    patch #6 is reviewed just for code implementation but that solution can't
>> convince all maintainers. Honestly, this is a rare possibility of collision
>> in real world and the original pci allocation is not good so its hard to
>> reshape the original mechanism in one week. But actually we also have some
>> other solutions but we need a little time to figure out how to step forward
>> but I just think any solution wouldn't bring any change to other stuffs.
>>    patch #7 is pretty close to be Acked.
>>
>> So what's your final determination?
>>
>
> If you and maintainers can work out a solution for hvmloader bits today
> then yes, otherwise no.
>

Based on my understanding, we already have some solutions but we need 
some time to put one into practice. I think its possible to work out 
this next week. As you see other stuffs are almost closed so we can put 
our all effort just on this bit.

Thanks
Tiejun

  reply	other threads:[~2015-07-17  9:24 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 [this message]
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
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=55A8C9E7.7080702@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.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).