>>> On 10.03.15 at 12:24, wrote:
> On 10/03/15 07:30, Jan Beulich wrote:
> On 09.03.15 at 19:49, wrote:
>>> On 09/03/15 16:08, Jan Beulich wrote:
Both PV and HVM logic have similar but not similar enough code here.
Synchronize the two so that
- in the HVM case we don't uncondit
On 10/03/15 07:30, Jan Beulich wrote:
On 09.03.15 at 19:49, wrote:
>> On 09/03/15 16:08, Jan Beulich wrote:
>>> Both PV and HVM logic have similar but not similar enough code here.
>>> Synchronize the two so that
>>> - in the HVM case we don't unconditionally try to access extended
>>> conf
>>> On 09.03.15 at 19:49, wrote:
> On 09/03/15 16:08, Jan Beulich wrote:
>> Both PV and HVM logic have similar but not similar enough code here.
>> Synchronize the two so that
>> - in the HVM case we don't unconditionally try to access extended
>> config space
>> - in the PV case we pass a corre
On 09/03/15 16:08, Jan Beulich wrote:
> Both PV and HVM logic have similar but not similar enough code here.
> Synchronize the two so that
> - in the HVM case we don't unconditionally try to access extended
> config space
> - in the PV case we pass a correct range to the XSM hook
> - in the PV ca
Both PV and HVM logic have similar but not similar enough code here.
Synchronize the two so that
- in the HVM case we don't unconditionally try to access extended
config space
- in the PV case we pass a correct range to the XSM hook
- in the PV case we don't needlessly deny access when the operat
