Uh... if you already have an A8-6600K there's no point in upgrading to Kaveri UNLESS you intend to use software which leverages HSA optimized branches of code for improved performance. I'm not aware of any mainstream software being developed and compiled to take advantage of HSA at this time.
You already have a "dual module/quad core" CPU, the A8-7600 is also a dual module quad core CPU. Kaveri is more refined, but not enough to makeup for the clock speed loss you would suffer going to the 65W 7600.
Due to the way that resources are shared in PileDriver architecture CPUs like your's, the Operating system task scheduler is configured to treat the second core of the same module as a "logical" core instead of a "physical" one for performance reasons. These are superficial distinctions used at the software level to ensure that multiple threads are assigned to separate modules whenever possible.
In the case of Intel Hyperthreading, the same scheduling technique is used, but the superficial distinction of "logical" vs "physical" is actually much more accurate, even though a haswell core has more execution resources than a piledriver module, those execution resources are still arranged into a single very wide execution engine. In A pileDriver module, there are indeed 2 distinct sets of equal execution engines that are effectively isolated (a single thread can not have work assigned on both of these execution engines simultaneously, it's physically impossible). The module does however, share a large front-end, instruction decoder, and FPU instruction engine across both cores. This is where the "grey line" problem comes in. For workloads that bottleneck on instruction decoders or the FPU piplines, it's more like a single core.