All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Li, ZhenHua" <zhen-hual@hp.com>
To: Baoquan He <bhe@redhat.com>
Cc: Minfei Huang <mhuang@redhat.com>,
	joro@8bytes.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	"Li, ZhenHua" <zhen-hual@hp.com>,
	dwmw2@infradead.org
Subject: Re: [PATCH 1/1] x86/iommu: fix incorrect bit operations in setting values
Date: Fri, 14 Nov 2014 16:12:02 +0800	[thread overview]
Message-ID: <5465B952.3010702@hp.com> (raw)
In-Reply-To: <54655B0F.5070204@hp.com>


> 1st step shows we should NOT disable the iommu when it is already
> enabled. But current code does disable-enable. So there is still works
> to do.
>

The original kernel does a disable and re-enable , Bill's patchset 
removed the disable operation.

> I think step 2 is necessary, because when the driver initializes, the
> device need a new map, and the old data from the old kernel can not be
> used for the new driver.
>
> Now I am trying to implement these ideas.
>
>> Thanks

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: "Li, ZhenHua" <zhen-hual-VXdhtT5mjnY@public.gmane.org>
To: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Minfei Huang <mhuang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	"Li, ZhenHua" <zhen-hual-VXdhtT5mjnY@public.gmane.org>,
	dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [PATCH 1/1] x86/iommu: fix incorrect bit operations in setting values
Date: Fri, 14 Nov 2014 16:12:02 +0800	[thread overview]
Message-ID: <5465B952.3010702@hp.com> (raw)
In-Reply-To: <54655B0F.5070204-VXdhtT5mjnY@public.gmane.org>


> 1st step shows we should NOT disable the iommu when it is already
> enabled. But current code does disable-enable. So there is still works
> to do.
>

The original kernel does a disable and re-enable , Bill's patchset 
removed the disable operation.

> I think step 2 is necessary, because when the driver initializes, the
> device need a new map, and the old data from the old kernel can not be
> used for the new driver.
>
> Now I am trying to implement these ideas.
>
>> Thanks

WARNING: multiple messages have this Message-ID (diff)
From: "Li, ZhenHua" <zhen-hual@hp.com>
To: Baoquan He <bhe@redhat.com>
Cc: "Li, ZhenHua" <zhen-hual@hp.com>,
	Minfei Huang <mhuang@redhat.com>,
	kexec@lists.infradead.org, joro@8bytes.org, dwmw2@infradead.org,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86/iommu: fix incorrect bit operations in setting values
Date: Fri, 14 Nov 2014 16:12:02 +0800	[thread overview]
Message-ID: <5465B952.3010702@hp.com> (raw)
In-Reply-To: <54655B0F.5070204@hp.com>


> 1st step shows we should NOT disable the iommu when it is already
> enabled. But current code does disable-enable. So there is still works
> to do.
>

The original kernel does a disable and re-enable , Bill's patchset 
removed the disable operation.

> I think step 2 is necessary, because when the driver initializes, the
> device need a new map, and the old data from the old kernel can not be
> used for the new driver.
>
> Now I am trying to implement these ideas.
>
>> Thanks

  reply	other threads:[~2014-11-14  8:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05  7:30 [PATCH 1/1] x86/iommu: fix incorrect bit operations in setting values Li, Zhen-Hua
2014-11-05  7:30 ` Li, Zhen-Hua
     [not found] ` <1415172619-4801-1-git-send-email-zhen-hual-VXdhtT5mjnY@public.gmane.org>
2014-11-05  7:35   ` Li, ZhenHua
2014-11-05  7:35     ` Li, ZhenHua
2014-11-06 13:41   ` Joerg Roedel
2014-11-06 13:41     ` Joerg Roedel
2014-11-12 11:28 ` Minfei Huang
2014-11-12 11:28   ` Minfei Huang
2014-11-12 11:28   ` Minfei Huang
2014-11-13  9:06   ` Li, ZhenHua
2014-11-13  9:06     ` Li, ZhenHua
2014-11-13  9:06     ` Li, ZhenHua
2014-11-13 13:37     ` Baoquan He
2014-11-13 13:37       ` Baoquan He
2014-11-13 13:37       ` Baoquan He
2014-11-14  1:29       ` Li, ZhenHua
2014-11-14  1:29         ` Li, ZhenHua
2014-11-14  1:29         ` Li, ZhenHua
2014-11-14  8:12         ` Li, ZhenHua [this message]
2014-11-14  8:12           ` Li, ZhenHua
2014-11-14  8:12           ` Li, ZhenHua

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5465B952.3010702@hp.com \
    --to=zhen-hual@hp.com \
    --cc=bhe@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhuang@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.