Merge ACPICA 20111123.

Requested by:
Ticket: #6265
Add support for WRITE ATOMIC (16) command and report SBC-4 compliance.

Atomic writes are only supported for ZVOLs in "dev" mode.  In other cases
atomicity can not be guarantied and so the command is blocked.

(cherry picked from commit 7bd2d46a11dd655647cc8a0922f6414b1ffad635)
Properly report 12Gbps connection rate.

Reviewed by:	kadesai, slm
MFC after:	1 week

(cherry picked from commit a6a73044a009d2159c47f23783709d616ca6e259)
Implement software (mode page) and hardware (config) write protection.

(cherry picked from commit c561a7a0862e17e6c7c2cd76ed43f98dc7893d33)
Add support for MaxBurstLength and Expected Data transfer Length parameters.

Before this change target could send R2T request for write transfer of any
size, that could violate iSCSI RFC, which allows initiator to limit maximum
R2T size by negotiating MaxBurstLength connection parameter.

Also report an error in case of write underflow, when initiator provides
less data than initiator expects.  Previously in such case our target
sent R2T request for non-existing data, violating the RFC, and confusing
some initiators.  SCSI specs don't explicitly define how write underflows
should be handled and there are different oppinions, but reporting error
is hopefully better then violating iSCSI RFC with unpredictable results.

MFC after:	2 weeks

(cherry picked from commit b69cab850310b0e88d9726ef1d38b6bf1fa8e2a9)
Update dialog to 1.2-20130923.

Ticket:	#6264
Revert "Update dialog to 1.2-20130923."

This reverts commit a1b3faebf6ab77911d28f1558dbca2e1859f355d.
Update dialog to 1.2-20130523
Level up WARNS

(cherry picked from commit 417e87f740ac4d85234428776a69e163d33517bd)
Update dialog to 1.2-20130923.

Approved by:	re (marius)

(cherry picked from commit 6633bf70ed24c304037f64ca2f28e6ea8d2a0b47)
Use the rounded size (psize) instead of asize for L2ARC space accounting.

Ticket: #6239