On Thu, Oct 18, 2018 at 03:38:58PM +0100, Daniel P. Berrangé wrote:
> On Thu, Oct 18, 2018 at 03:15:31PM +0100, Peter Maydell wrote:
> > On 18 October 2018 at 15:11, Marcel Apfelbaum
> > wrote:
> > > Maybe would be a step toward a clean "socket-device" modeling (what goes
> > > where)
> > > and al
On 10/18/18 5:48 PM, Peter Maydell wrote:
On 18 October 2018 at 15:45, Marcel Apfelbaum
wrote:
PCIe machines support PCI devices while PCI machines do not support
PCIe devices.
I think users of the PCI machines would benefit from having a clear list of
supported devices, rather than have to
On 10/18/18 5:41 PM, Peter Maydell wrote:
On 18 October 2018 at 15:38, Daniel P. Berrangé wrote:
On Thu, Oct 18, 2018 at 03:15:31PM +0100, Peter Maydell wrote:
On 18 October 2018 at 15:11, Marcel Apfelbaum
wrote:
Maybe would be a step toward a clean "socket-device" modeling (what goes
whe
On Thu, Oct 18, 2018 at 03:15:31PM +0100, Peter Maydell wrote:
> On 18 October 2018 at 15:11, Marcel Apfelbaum
> wrote:
> > Maybe would be a step toward a clean "socket-device" modeling (what goes
> > where)
> > and also QEMU emulation would be cleaner since in bare metal you cannot
> > plug a PCI
On 18 October 2018 at 15:45, Marcel Apfelbaum
wrote:
> PCIe machines support PCI devices while PCI machines do not support
> PCIe devices.
>
> I think users of the PCI machines would benefit from having a clear list of
> supported devices, rather than have to find out if their device
> 1. Is a hy
On 18 October 2018 at 15:38, Daniel P. Berrangé wrote:
> On Thu, Oct 18, 2018 at 03:15:31PM +0100, Peter Maydell wrote:
>> On 18 October 2018 at 15:11, Marcel Apfelbaum
>> wrote:
>> > Maybe would be a step toward a clean "socket-device" modeling (what goes
>> > where)
>> > and also QEMU emulation
On 18 October 2018 at 15:11, Marcel Apfelbaum
wrote:
> Maybe would be a step toward a clean "socket-device" modeling (what goes
> where)
> and also QEMU emulation would be cleaner since in bare metal you cannot
> plug a PCIe device into a PCI slot and vice-versa or have the same device ID
> for bo
Hi Eduardo,
On 10/17/18 6:56 PM, Eduardo Habkost wrote:
(CCing Marcel, in case he has extra details on the complex
Conventional/Express bus/device plugging rules)
On Wed, Oct 17, 2018 at 07:57:39AM +0200, Markus Armbruster wrote:
Laine Stump writes:
[...]
In the end, having a device that ch
On Wed, Oct 17, 2018 at 12:38:29PM -0400, Michael S. Tsirkin wrote:
> On Wed, Oct 17, 2018 at 12:56:37PM -0300, Eduardo Habkost wrote:
> > (CCing Marcel, in case he has extra details on the complex
> > Conventional/Express bus/device plugging rules)
> >
> > On Wed, Oct 17, 2018 at 07:57:39AM +0200
On Wed, Oct 17, 2018 at 12:56:37PM -0300, Eduardo Habkost wrote:
> (CCing Marcel, in case he has extra details on the complex
> Conventional/Express bus/device plugging rules)
>
> On Wed, Oct 17, 2018 at 07:57:39AM +0200, Markus Armbruster wrote:
> > Laine Stump writes:
> >
> > [...]
> > > In th
(CCing Marcel, in case he has extra details on the complex
Conventional/Express bus/device plugging rules)
On Wed, Oct 17, 2018 at 07:57:39AM +0200, Markus Armbruster wrote:
> Laine Stump writes:
>
> [...]
> > In the end, having a device that changed PCI ID depending on what kind
> > of slot it
Gerd Hoffmann writes:
> On Wed, Oct 17, 2018 at 07:57:39AM +0200, Markus Armbruster wrote:
>> Laine Stump writes:
>>
>> [...]
>> > In the end, having a device that changed PCI ID depending on what kind
>> > of slot it was plugged into was an idea "too clever for its own good",
>> > should be av
On Wed, Oct 17, 2018 at 07:57:39AM +0200, Markus Armbruster wrote:
> Laine Stump writes:
>
> [...]
> > In the end, having a device that changed PCI ID depending on what kind
> > of slot it was plugged into was an idea "too clever for its own good",
> > should be avoided when new devices are added
Laine Stump writes:
[...]
> In the end, having a device that changed PCI ID depending on what kind
> of slot it was plugged into was an idea "too clever for its own good",
> should be avoided when new devices are added in the future, and we
> should at least provide an alternative that doesn't do
14 matches
Mail list logo