public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Wang, Xiaoming" <xiaoming.wang@intel.com>
Cc: Jan Beulich <JBeulich@suse.com>,
	"Liu@aserp2030.oracle.com" <Liu@aserp2030.oracle.com>,
	"Zhang@aserp2030.oracle.com" <Zhang@aserp2030.oracle.com>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
	"david.vrabel@citrix.com" <david.vrabel@citrix.com>,
	"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
	"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
	"linux@horizon.com" <linux@horizon.com>,
	"Liu, Chuansheng" <chuansheng.liu@intel.com>,
	"Zhang, Dongxing" <dongxing.zhang@intel.com>,
	"takahiro.akashi@linaro.org" <takahiro.akashi@linaro.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
	"d.kasatkin@samsung.com" <d.kasatkin@samsung.com>,
	"pebolle@tiscali.nl" <pebolle@tiscali.nl>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jkosina@suse.cz" <jkosina@suse.cz>
Subject: Re: [PATCH v5] modify the IO_TLB_SEGSIZE and IO_TLB_DEFAULT_SIZE configurable as flexible requirement about SW-IOMMU.
Date: Fri, 6 Mar 2015 10:19:31 -0500	[thread overview]
Message-ID: <20150306151931.GC4808@l.oracle.com> (raw)
In-Reply-To: <FA47D36D6EC9FE4CB463299737C09B9901D061EB@shsmsx102.ccr.corp.intel.com>

. snip..

> Format: { <int>,force,<int>,<int>} is suitable I think.
> And fixing  "force" is follow the code design previously in setup_io_tlb_npages.

It is a bug. It should have been smart enough to deal with the 'force' being
in any order.

If you are willing to make a patch to fix this - either folded into this
patch I am responding to or as a seperate one - that would be most excellent!

However, I can also do it - but my plate is full so it will take me some time
to get to it.

  reply	other threads:[~2015-03-06 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  8:11 [PATCH v5] modify the IO_TLB_SEGSIZE and IO_TLB_DEFAULT_SIZE configurable as flexible requirement about SW-IOMMU Wang Xiaoming
2015-03-04 19:42 ` Konrad Rzeszutek Wilk
2015-03-05  3:53   ` Wang, Xiaoming
2015-03-05  8:40     ` Jan Beulich
2015-03-05  8:52       ` Wang, Xiaoming
2015-03-05  9:00         ` Jan Beulich
2015-03-06  1:12           ` Wang, Xiaoming
2015-03-06 15:19             ` Konrad Rzeszutek Wilk [this message]
2015-03-09  0:31               ` Wang, Xiaoming

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=20150306151931.GC4808@l.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=Liu@aserp2030.oracle.com \
    --cc=Zhang@aserp2030.oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=chuansheng.liu@intel.com \
    --cc=d.kasatkin@samsung.com \
    --cc=david.vrabel@citrix.com \
    --cc=dongxing.zhang@intel.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jkosina@suse.cz \
    --cc=lauraa@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux@horizon.com \
    --cc=pebolle@tiscali.nl \
    --cc=ralf@linux-mips.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xiaoming.wang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox