On Fri, Feb 17, 2017 at 02:01:15PM -0600, Venu Busireddy wrote:
> On Fri, Feb 17, 2017 at 02:29:32PM -0500, Konrad Rzeszutek Wilk wrote:
> > On Fri, Feb 17, 2017 at 12:27:25PM -0700, Tamas K Lengyel wrote:
> > > On Fri, Feb 17, 2017 at 11:56 AM, Konrad Rzeszutek Wilk
> > >
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Friday, February 17, 2017 4:21 PM
>
> I think the commit description is pretty clear. Especially this part
>
> "This could have the nice side effect of allowing to use "iommu=off"
> even when x2APIC was pre-enabled by the BIOS (in which
On Fri, Feb 17, 2017 at 2:31 PM, Andrew Cooper
wrote:
> On 17/02/17 21:28, Tamas K Lengyel wrote:
>> On Fri, Feb 17, 2017 at 1:01 PM, Venu Busireddy
>> wrote:
>>> On Fri, Feb 17, 2017 at 02:29:32PM -0500, Konrad Rzeszutek Wilk wrote:
On
On 17/02/17 21:28, Tamas K Lengyel wrote:
> On Fri, Feb 17, 2017 at 1:01 PM, Venu Busireddy
> wrote:
>> On Fri, Feb 17, 2017 at 02:29:32PM -0500, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Feb 17, 2017 at 12:27:25PM -0700, Tamas K Lengyel wrote:
On Fri, Feb 17, 2017
On Fri, Feb 17, 2017 at 1:01 PM, Venu Busireddy
wrote:
> On Fri, Feb 17, 2017 at 02:29:32PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Fri, Feb 17, 2017 at 12:27:25PM -0700, Tamas K Lengyel wrote:
>> > On Fri, Feb 17, 2017 at 11:56 AM, Konrad Rzeszutek Wilk
>> >
On Fri, Feb 17, 2017 at 02:29:32PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Feb 17, 2017 at 12:27:25PM -0700, Tamas K Lengyel wrote:
> > On Fri, Feb 17, 2017 at 11:56 AM, Konrad Rzeszutek Wilk
> > wrote:
> > > . snip..
> > >> >> > Given this commit is pretty old, I'm
On Fri, Feb 17, 2017 at 12:27:25PM -0700, Tamas K Lengyel wrote:
> On Fri, Feb 17, 2017 at 11:56 AM, Konrad Rzeszutek Wilk
> wrote:
> > . snip..
> >> >> > Given this commit is pretty old, I'm also curious why it's only
> >> >> > reported
> >> >> > on 4.8. Tamas, did you
On Fri, Feb 17, 2017 at 11:56 AM, Konrad Rzeszutek Wilk
wrote:
> . snip..
>> >> > Given this commit is pretty old, I'm also curious why it's only reported
>> >> > on 4.8. Tamas, did you succeed with iommu=0 pre 4.8, or 4.8 happens
>> >> > to be the one upon which you first
. snip..
> >> > Given this commit is pretty old, I'm also curious why it's only reported
> >> > on 4.8. Tamas, did you succeed with iommu=0 pre 4.8, or 4.8 happens
> >> > to be the one upon which you first tried iommu=0 on a platform supporting
> >> > interrupt remapping?
> >>
> >> It just happens
On Fri, Feb 17, 2017 at 11:48 AM, Konrad Rzeszutek Wilk
wrote:
> On Fri, Feb 17, 2017 at 11:42:20AM -0700, Tamas K Lengyel wrote:
>> On Thu, Feb 16, 2017 at 11:53 PM, Tian, Kevin wrote:
>> >> From: Tian, Kevin
>> >> Sent: Friday, February 17, 2017
On Fri, Feb 17, 2017 at 11:42:20AM -0700, Tamas K Lengyel wrote:
> On Thu, Feb 16, 2017 at 11:53 PM, Tian, Kevin wrote:
> >> From: Tian, Kevin
> >> Sent: Friday, February 17, 2017 11:35 AM
> >> > >>
> >> > >> Or wait - do you have the same issue if you use
> >> > >>
On Thu, Feb 16, 2017 at 11:53 PM, Tian, Kevin wrote:
>> From: Tian, Kevin
>> Sent: Friday, February 17, 2017 11:35 AM
>> > >>
>> > >> Or wait - do you have the same issue if you use
>> > >> "iommu=no,no-intremap"? In which case the problem would be
>> > >> that "iommu=no"
On Fri, Feb 17, 2017 at 1:20 AM, Jan Beulich wrote:
On 17.02.17 at 07:53, wrote:
>>> From: Tian, Kevin
>>> Sent: Friday, February 17, 2017 11:35 AM
>>> > >>
>>> > >> Or wait - do you have the same issue if you use
>>> > >> "iommu=no,no-intremap"? In
>>> On 17.02.17 at 07:53, wrote:
>> From: Tian, Kevin
>> Sent: Friday, February 17, 2017 11:35 AM
>> > >>
>> > >> Or wait - do you have the same issue if you use
>> > >> "iommu=no,no-intremap"? In which case the problem would be
>> > >> that "iommu=no" should clear more
>>> On 17.02.17 at 04:35, wrote:
> Feng just left Intel. Let me take a look at code to understand the
> rationale behind.
Do you know if he means to stay VT-d maintainer? If yes, do you
have a new email address of him? If not, would you mind sending
an update to
> From: Tian, Kevin
> Sent: Friday, February 17, 2017 11:35 AM
> > >>
> > >> Or wait - do you have the same issue if you use
> > >> "iommu=no,no-intremap"? In which case the problem would be
> > >> that "iommu=no" should clear more than just "iommu_enable", or
> > >> code checking iommu_intremap
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, February 16, 2017 5:32 PM
>
> >>> On 15.02.17 at 20:30, wrote:
> > On Wed, Feb 15, 2017 at 3:03 AM, Jan Beulich wrote:
> > On 15.02.17 at 00:21, wrote:
>>> On 15.02.17 at 20:30, wrote:
> On Wed, Feb 15, 2017 at 3:03 AM, Jan Beulich wrote:
> On 15.02.17 at 00:21, wrote:
>>> On 14/02/2017 22:47, Tamas K Lengyel wrote:
(XEN) Switched to APIC driver x2apic_cluster.
On Wed, Feb 15, 2017 at 12:30 PM, Tamas K Lengyel
wrote:
> On Wed, Feb 15, 2017 at 3:03 AM, Jan Beulich wrote:
> On 15.02.17 at 00:21, wrote:
>>> On 14/02/2017 22:47, Tamas K Lengyel wrote:
(XEN) Switched to APIC
On Wed, Feb 15, 2017 at 3:03 AM, Jan Beulich wrote:
On 15.02.17 at 00:21, wrote:
>> On 14/02/2017 22:47, Tamas K Lengyel wrote:
>>> (XEN) Switched to APIC driver x2apic_cluster.
>>> (XEN) XSM Framework v1.0.0 initialized
>>> (XEN) Flask: 128
>>> On 15.02.17 at 00:21, wrote:
> On 14/02/2017 22:47, Tamas K Lengyel wrote:
>> (XEN) Switched to APIC driver x2apic_cluster.
>> (XEN) XSM Framework v1.0.0 initialized
>> (XEN) Flask: 128 avtab hash slots, 394 rules.
>> (XEN) Flask: 128 avtab hash slots, 394 rules.
>>
On 14/02/2017 22:47, Tamas K Lengyel wrote:
> (XEN) Switched to APIC driver x2apic_cluster.
> (XEN) XSM Framework v1.0.0 initialized
> (XEN) Flask: 128 avtab hash slots, 394 rules.
> (XEN) Flask: 128 avtab hash slots, 394 rules.
> (XEN) Flask: 5 users, 3 roles, 43 types, 2 bools
> (XEN) Flask:
Hi all,
I'm having some strange issues with Xen 4.8 when I try to boot with
iommu disabled.
(XEN) Xen version 4.8.0 (root@lan) (gcc (Debian 5.4.1-4) 5.4.1
20161202) debug=n Tue Feb 14 15:32:55 MST 2017
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.02~beta3-4
(XEN) Command line: placeholder
23 matches
Mail list logo