[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-19 Thread Inki Dae
Hi Rob, 2013/3/19 Rob Clark : > On Mon, Mar 18, 2013 at 9:32 PM, YoungJun Cho wrote: >> >> On Mar 19, 2013 9:55 AM, "Rob Clark" wrote: >>> >>> On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho >>> wrote: >>> > >>> > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: >>> >> >>> >> Btw, what is the hw res

[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-19 Thread YoungJun Cho
On Mar 19, 2013 9:55 AM, "Rob Clark" wrote: > > On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho wrote: > > > > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: > >> > >> Btw, what is the hw response to invalid input (ie. bottom>top, invalid > >> size, etc)? > >> > > > > Unfortunately the IOMMU page fau

[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-19 Thread YoungJun Cho
On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: > > Btw, what is the hw response to invalid input (ie. bottom>top, invalid > size, etc)? > Unfortunately the IOMMU page fault is happened. So we need some codes for protecting kernel. Thank you~ Best regards YJ > Ie. if it will just ignore the blit or

Re: [PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread Inki Dae
Hi Rob, 2013/3/19 Rob Clark : > On Mon, Mar 18, 2013 at 9:32 PM, YoungJun Cho wrote: >> >> On Mar 19, 2013 9:55 AM, "Rob Clark" wrote: >>> >>> On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho >>> wrote: >>> > >>> > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: >>> >> >>> >> Btw, what is the hw res

[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread Rob Clark
On Mon, Mar 18, 2013 at 9:32 PM, YoungJun Cho wrote: > > On Mar 19, 2013 9:55 AM, "Rob Clark" wrote: >> >> On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho >> wrote: >> > >> > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: >> >> >> >> Btw, what is the hw response to invalid input (ie. bottom>top, inv

[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread Rob Clark
On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho wrote: > > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: >> >> Btw, what is the hw response to invalid input (ie. bottom>top, invalid >> size, etc)? >> > > Unfortunately the IOMMU page fault is happened. So we need some codes for > protecting kernel. h

Re: [PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread Rob Clark
On Mon, Mar 18, 2013 at 9:32 PM, YoungJun Cho wrote: > > On Mar 19, 2013 9:55 AM, "Rob Clark" wrote: >> >> On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho >> wrote: >> > >> > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: >> >> >> >> Btw, what is the hw response to invalid input (ie. bottom>top, inv

Re: [PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread YoungJun Cho
On Mar 19, 2013 9:55 AM, "Rob Clark" wrote: > > On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho wrote: > > > > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: > >> > >> Btw, what is the hw response to invalid input (ie. bottom>top, invalid > >> size, etc)? > >> > > > > Unfortunately the IOMMU page fau

Re: [PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread Rob Clark
On Mon, Mar 18, 2013 at 8:00 PM, YoungJun Cho wrote: > > On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: >> >> Btw, what is the hw response to invalid input (ie. bottom>top, invalid >> size, etc)? >> > > Unfortunately the IOMMU page fault is happened. So we need some codes for > protecting kernel. h

Re: [PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread YoungJun Cho
On Mar 19, 2013 3:01 AM, "Rob Clark" wrote: > > Btw, what is the hw response to invalid input (ie. bottom>top, invalid > size, etc)? > Unfortunately the IOMMU page fault is happened. So we need some codes for protecting kernel. Thank you~ Best regards YJ > Ie. if it will just ignore the blit or

[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread Rob Clark
Btw, what is the hw response to invalid input (ie. bottom>top, invalid size, etc)? Ie. if it will just ignore the blit or raise an error irq which can be handled sanely, it could be ok to avoid the overhead of the cmdstream checking in the kernel. The kernel part really just needs to ensure that

Re: [PATCH 0/7] Consider G2D hardware restrictions.

2013-03-18 Thread Rob Clark
Btw, what is the hw response to invalid input (ie. bottom>top, invalid size, etc)? Ie. if it will just ignore the blit or raise an error irq which can be handled sanely, it could be ok to avoid the overhead of the cmdstream checking in the kernel. The kernel part really just needs to ensure that

[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-13 Thread Inki Dae
This patch set checks the contents of g2d command list from user is valid or not according to G2D hardware restrictions. For now, G2D driver wasn't considered for them properly. For this, this patch set includes relevant code cleaups, fixups and adds a new function to get buffer size to the gem to

[PATCH 0/7] Consider G2D hardware restrictions.

2013-03-13 Thread Inki Dae
This patch set checks the contents of g2d command list from user is valid or not according to G2D hardware restrictions. For now, G2D driver wasn't considered for them properly. For this, this patch set includes relevant code cleaups, fixups and adds a new function to get buffer size to the gem to