I would interprete it the same as rjain. Yes, it would be possible to implement, but AMD just hasn't done so. In reality, they might not ever need to implement. I remember reading that AMD was experimenting with multi-core processors, which instread of being hyperthreaded, would be true multi-threaded.
Hyperthreaded is not a bad idea, especially with Intel's current line of P4 processors. Analysis has shown that many of the CPU's clock cycles were being wasted on the P4 architecture while waiting for I/O or flushing the processor pipeline to allow a different set of operations to be performed. So they pretty much gave the processor a second pipeline (well almost certain parts of the processor can still only perform an operation/action on one of the pipelines at a time so there are still bottlenecks). The addition of this additional pipeline allows the P4 with hyperthreading to be able to cut back on the wasted clock cycles by allowing another "thread" of operations to be executed while another thread stopped because of I/O, or a flush (or any number of reasons that would cause the pipeline to be delayed from being processed).
This allows the impression of a multi-threaded hardware. It is not true multi-threaded as that would involve being able to process 2 or more threads concurrently (i.e. at the same time), while hyperthreading can still only actually process one thread at any given time. AMD's multi-core system would be true multi-threaded and not hyperthreaded. Hyperthreading was simply a way to increase performance of the P4 by utilizing more of the wasted clock cycles.
AMD's CPU's have tended to be more efficient in terms of utilizing more of its clock cycles then Intel's P4 line. Partly due to the pipeline structure as well as allowing more time for each clock cycle to complete (i.e. a faster Hz rating means there is less time availabe for a clock cycle to complete, and with I/O (i.e. reading from memory, or hard drive, etc) taking a certain amount of time, multiple clock cycles are wasted while waiting for that I/O to complete, whereas with a slightly longer clock cycle, more I/O has a chance to complete in less clock cycles, thus not wasting as many cycles as the faster clock cycle system might waste). Hyperthreading was a way to make the P4 more efficient in its operations, and would not necessarily make ALL CPU's more efficient.