On 14.06.2011, at 20:18, Stefano Stabellini wrote:
> On Tue, 14 Jun 2011, Jan Kiszka wrote:
>> On 2011-06-14 15:27, Stefano Stabellini wrote:
>>> On Tue, 14 Jun 2011, Alexander Graf wrote:
> static int i440fx_load_old(QEMUFile* f, void *opaque, int version_id)
> {
> PCII4
On Tue, 14 Jun 2011, Jan Kiszka wrote:
> On 2011-06-14 15:27, Stefano Stabellini wrote:
> > On Tue, 14 Jun 2011, Alexander Graf wrote:
> >>> static int i440fx_load_old(QEMUFile* f, void *opaque, int version_id)
> >>> {
> >>> PCII440FXState *d = opaque;
> >>> @@ -267,8 +263,17 @@ s
On 2011-06-14 15:27, Stefano Stabellini wrote:
> On Tue, 14 Jun 2011, Alexander Graf wrote:
>>> static int i440fx_load_old(QEMUFile* f, void *opaque, int version_id)
>>> {
>>> PCII440FXState *d = opaque;
>>> @@ -267,8 +263,17 @@ static PCIBus *i440fx_common_init(const char
>>
On Tue, 14 Jun 2011, Jan Kiszka wrote:
> I bet the motivation is to have an IRQ route that is independent of
> QEMU, thus can be discovered inside the Xen kernel and then remains
> stable - or is simply hard-wired. Device assignment? Direct legacy IRQ
> injection from the kernel?
>
This code pred
On 2011-06-14 14:30, Alexander Graf wrote:
>
> Am 14.06.2011 um 14:17 schrieb Ian Campbell :
>
>> On Tue, 2011-06-14 at 10:25 +0100, Alexander Graf wrote:
>>> On 31.05.2011, at 13:05, Stefano Stabellini wrote:
>>>
On Sat, 28 May 2011, Alexander Graf wrote:
>
> On 26.05.2011, at 17:48
On 31.05.2011, at 13:05, Stefano Stabellini wrote:
> On Sat, 28 May 2011, Alexander Graf wrote:
>>
>> On 26.05.2011, at 17:48, Stefano Stabellini wrote:
>>
>>> xen: fix interrupt routing
>>>
>>> - remove i440FX-xen and i440fx_write_config_xen
>>> we don't need to intercept pci config writes to
On Sat, 28 May 2011, Alexander Graf wrote:
>
> On 26.05.2011, at 17:48, Stefano Stabellini wrote:
>
> > xen: fix interrupt routing
> >
> > - remove i440FX-xen and i440fx_write_config_xen
> > we don't need to intercept pci config writes to i440FX anymore;
>
> Why not? In which version? Did anyth
On 26.05.2011, at 17:48, Stefano Stabellini wrote:
> xen: fix interrupt routing
>
> - remove i440FX-xen and i440fx_write_config_xen
> we don't need to intercept pci config writes to i440FX anymore;
Why not? In which version? Did anything below change? What about compat code?
Older hypervisor v
xen: fix interrupt routing
- remove i440FX-xen and i440fx_write_config_xen
we don't need to intercept pci config writes to i440FX anymore;
- introduce PIIX3-xen and piix3_write_config_xen
we do need to intercept pci config write to the PCI-ISA bridge to update
the PCI link routing;
- set the num
On Thu, 19 May 2011, Isaku Yamahata wrote:
> On Wed, May 18, 2011 at 06:53:40PM +0100, stefano.stabell...@eu.citrix.com
> wrote:
> > From: Stefano Stabellini
> >
> > Match the routing informations built by seabios:
> >
> > - remove i440fx_write_config_xen
> > we don't need to intercept pci conf
On Wed, May 18, 2011 at 06:53:40PM +0100, stefano.stabell...@eu.citrix.com
wrote:
> From: Stefano Stabellini
>
> Match the routing informations built by seabios:
>
> - remove i440fx_write_config_xen
> we don't need to intercept pci config writes to i440FX;
>
> - introduce piix3_write_config_xe
From: Stefano Stabellini
Match the routing informations built by seabios:
- remove i440fx_write_config_xen
we don't need to intercept pci config writes to i440FX;
- introduce piix3_write_config_xen
we do need to intercept pci config write to the PCI-ISA bridge to update
the PCI link routing;
-
12 matches
Mail list logo