On 2016年09月23日 13:26, Peter Xu wrote:
> On Thu, Sep 22, 2016 at 12:34:36PM +0800, Chao Gao wrote:
>> Hi, we had 3 problems left here.
>> 1. IRQremapping can't work with x2apic_cluster mode.
>> 2. apic_id > 255 can't receive devices interrupts.
>> 3. windows crash when present IRQremapping capabilit
On Thu, Sep 22, 2016 at 12:34:36PM +0800, Chao Gao wrote:
> Hi, we had 3 problems left here.
> 1. IRQremapping can't work with x2apic_cluster mode.
> 2. apic_id > 255 can't receive devices interrupts.
> 3. windows crash when present IRQremapping capability to it.
For (3), I don't know whether it's
Hi, we had 3 problems left here.
1. IRQremapping can't work with x2apic_cluster mode.
2. apic_id > 255 can't receive devices interrupts.
3. windows crash when present IRQremapping capability to it.
I test with latest kernel v4.8-rc7 and find all of them are unsolved.
Also in the qemu and kernel co
On Thu, 11 Aug 2016 13:10:57 +0800
Peter Xu wrote:
> On Wed, Aug 10, 2016 at 10:51:51AM +0200, Igor Mammedov wrote:
>
> [...]
>
> > > > Upstream guest kernel 4.7.0+ (d52bd54db) crashes when booting with irq
> > > > remapping on:
> > > >
> > > > ./qemu-system-x86_64 -enable-kvm -smp
> > > > 1
On Wed, Aug 10, 2016 at 10:51:51AM +0200, Igor Mammedov wrote:
[...]
> > > Upstream guest kernel 4.7.0+ (d52bd54db) crashes when booting with irq
> > > remapping on:
> > >
> > > ./qemu-system-x86_64 -enable-kvm -smp
> > > 1,sockets=9,cores=32,threads=1,maxcpus=288 -device
> > > qemu64-x86_64-
On Tue, 9 Aug 2016 21:35:04 +0800
Peter Xu wrote:
> On Tue, Aug 09, 2016 at 10:28:41AM +0200, Igor Mammedov wrote:
> > On Mon, 8 Aug 2016 16:57:14 +0800
> > Peter Xu wrote:
> >
> > > On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> > > > HI, everyone.
> > > >
> > > > We have don
On Tue, 9 Aug 2016 21:35:04 +0800
Peter Xu wrote:
> On Tue, Aug 09, 2016 at 10:28:41AM +0200, Igor Mammedov wrote:
> > On Mon, 8 Aug 2016 16:57:14 +0800
> > Peter Xu wrote:
> >
> > > On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> > > > HI, everyone.
> > > >
> > > > We have don
On Tue, Aug 09, 2016 at 10:28:41AM +0200, Igor Mammedov wrote:
> On Mon, 8 Aug 2016 16:57:14 +0800
> Peter Xu wrote:
>
> > On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> > > HI, everyone.
> > >
> > > We have done some tests after merging this patch set into the lastest qemu
> > > ma
2016-08-09 16:19+0800, Chao Gao:
> On Tue, Aug 09, 2016 at 02:18:15PM +0800, Peter Xu wrote:
>>On Tue, Aug 09, 2016 at 12:33:17PM +0800, Chao Gao wrote:
>>> On Mon, Aug 08, 2016 at 04:57:14PM +0800, Peter Xu wrote:
>>> >On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
>>> >> HI, everyone.
2016-08-09 15:09+0800, Peter Xu:
> On Tue, Aug 09, 2016 at 08:33:13AM +0200, Jan Kiszka wrote:
>> On 2016-08-09 08:24, Peter Xu wrote:
>> > On Tue, Aug 09, 2016 at 02:18:15PM +0800, Peter Xu wrote:
>> >> On Tue, Aug 09, 2016 at 12:33:17PM +0800, Chao Gao wrote:
>> >>> On Mon, Aug 08, 2016 at 04:57:
On Mon, 8 Aug 2016 16:57:14 +0800
Peter Xu wrote:
> On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> > HI, everyone.
> >
> > We have done some tests after merging this patch set into the lastest qemu
> > master. In kvm aspect, we use the lastest kvm linux-next branch. Here are
> > som
On Tue, 9 Aug 2016 11:23:58 +0800
Chao Gao wrote:
> On Mon, Aug 08, 2016 at 11:18:20AM +0200, Igor Mammedov wrote:
> >On Mon, 8 Aug 2016 15:41:23 +0800
> >Chao Gao wrote:
> >
> >> HI, everyone.
> >>
> >> We have done some tests after merging this patch set into the lastest qemu
> >> master. I
On Tue, Aug 09, 2016 at 02:18:15PM +0800, Peter Xu wrote:
>On Tue, Aug 09, 2016 at 12:33:17PM +0800, Chao Gao wrote:
>> On Mon, Aug 08, 2016 at 04:57:14PM +0800, Peter Xu wrote:
>> >On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
>> >> HI, everyone.
>> >>
>> >> We have done some tests af
On Tue, Aug 09, 2016 at 08:33:13AM +0200, Jan Kiszka wrote:
> On 2016-08-09 08:24, Peter Xu wrote:
> > On Tue, Aug 09, 2016 at 02:18:15PM +0800, Peter Xu wrote:
> >> On Tue, Aug 09, 2016 at 12:33:17PM +0800, Chao Gao wrote:
> >>> On Mon, Aug 08, 2016 at 04:57:14PM +0800, Peter Xu wrote:
> On M
On 2016-08-09 08:24, Peter Xu wrote:
> On Tue, Aug 09, 2016 at 02:18:15PM +0800, Peter Xu wrote:
>> On Tue, Aug 09, 2016 at 12:33:17PM +0800, Chao Gao wrote:
>>> On Mon, Aug 08, 2016 at 04:57:14PM +0800, Peter Xu wrote:
On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> HI, everyo
On Tue, Aug 09, 2016 at 02:18:15PM +0800, Peter Xu wrote:
> On Tue, Aug 09, 2016 at 12:33:17PM +0800, Chao Gao wrote:
> > On Mon, Aug 08, 2016 at 04:57:14PM +0800, Peter Xu wrote:
> > >On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> > >> HI, everyone.
> > >>
> > >> We have done some te
On Tue, Aug 09, 2016 at 12:33:17PM +0800, Chao Gao wrote:
> On Mon, Aug 08, 2016 at 04:57:14PM +0800, Peter Xu wrote:
> >On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> >> HI, everyone.
> >>
> >> We have done some tests after merging this patch set into the lastest qemu
> >> master. In
On Mon, Aug 08, 2016 at 04:57:14PM +0800, Peter Xu wrote:
>On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
>> HI, everyone.
>>
>> We have done some tests after merging this patch set into the lastest qemu
>> master. In kvm aspect, we use the lastest kvm linux-next branch. Here are
>> som
On Mon, Aug 08, 2016 at 11:18:20AM +0200, Igor Mammedov wrote:
>On Mon, 8 Aug 2016 15:41:23 +0800
>Chao Gao wrote:
>
>> HI, everyone.
>>
>> We have done some tests after merging this patch set into the lastest qemu
>> master. In kvm aspect, we use the lastest kvm linux-next branch. Here are
>> so
On Mon, 8 Aug 2016 15:41:23 +0800
Chao Gao wrote:
> HI, everyone.
>
> We have done some tests after merging this patch set into the lastest qemu
> master. In kvm aspect, we use the lastest kvm linux-next branch. Here are
> some problems we have met.
>
> 1. We can't boot up a 288 vcpus linux gue
On Mon, Aug 08, 2016 at 03:41:23PM +0800, Chao Gao wrote:
> HI, everyone.
>
> We have done some tests after merging this patch set into the lastest qemu
> master. In kvm aspect, we use the lastest kvm linux-next branch. Here are
> some problems we have met.
>
> 1. We can't boot up a 288 vcpus lin
Changes since RFC:
- use new KVM_CAP_X2APIC_API to detect x2APIC IDs support
- rebase on top of 2.7-rc1, since many deps were merged
- fix etc/boot-cpus to account for -device provided cpus
- include not yet merged _PXM fix as prereq
- add 2.8 machine type and bump up maxcpus count since
22 matches
Mail list logo