Background

[0001 ] This relates generally to computing and particularly processing.

[0002] In order to be compatible with previous generations of processors, a subsequent generation generally includes support for legacy features. Over time, some of these legacy features become less and less commonly used since developers tend to revise their programs to work with the most current instruction sets. As time goes on, the number of legacy instructions that need to be supported continually increases. Nonetheless these legacy instructions may be executed less and less often.

Brief Description Of The Drawings

[0003] Some embodiments are described with respect to the following figures:

Figure 1 Figure 1 is a flow chart for one embodiment of the present invention; Figure 2 is a schematic depiction of one embodiment to the present invention; Figure 3 is a flow chart for another embodiment to the present invention; Figure 4 is a flow chart for still another embodiment to the present invention; and

Figure 5 is a hardware depiction for yet another embodiment to the present invention.

Detailed Description

[0004] In accordance with some embodiments, a processor may be built with a partial core that only executes a partial set of the total instructions, by eliminating some instructions needed to be fully backwards compliant. Thus, in some embodiments power consumption may be reduced by providing partial cores that only execute certain instructions and not other instructions needed to be backwards compliant. The instructions not supported may be handled in other, more energy efficient ways, so that, the overall processor, including the partial core, may be fully backwards compliant. But the processor core may operate on the bulk of the instructions that are used in current generations of processors without having to support legacy instructions. This may mean that in some cases, the partial core processors may be more energy efficient.

[0005] For example, a partial core may eliminate a variety of different

instructions. In one embodiment, a partial core may eliminate microcode read-only memory dependencies. In such case, the partial core instructions are implemented as a single operation instruction. Thus, the instructions get directly translated in hardware without needing to fetch corresponding microoperations from the microcode read-only memory as is commonly done with complete or non-partial processors. This may save a significant amount of microcode read-only memory space.

[0006] In addition, only a subset of those instructions that are available on complete cores are actually used by modern compilers. As a result of architecture evolution over the last couple of decades, commercial instructions set architectures have many obsolete or non-useful instructions that can be eliminated for efficiency but at the cost of some lack of backwards compatibility.

[0007] Features from previous generations like 16-bit real mode from the Microsoft Disk Operating System (DOS) days and segmentation based memory protection architecture, local and global descriptor tables are being carried forward for backward compatibility reasons. But most modern operating systems do not need or use these features anymore. Thus, in some embodiments these features may simply be eliminated from partial cores.

[0008] Thus, in one embodiment, the partial core may be legacy-free or non- backwards compliant. This may make the core more energy efficient and particularly suitable for embedded applications. Other examples may include reducing the number of floating point and single-instruction multiple data instructions as well as support for caches. Only integer and scalar instructions set architecture subsets may be implemented in one embodiment of a partial core. The same idea can be extended to floating point and vector (single instruction multiple data) instruction sets as well as to features typically implemented by full cores. The partial core is simply an implementation of a subset architecture that in some embodiments may be targeted to embedded applications. Other implementations of a subset architecture include different numbers of pipelined stages and other performance features like out-of-order, super scalar, caches to make these partial cores suitable for particular market segments such as personal computers, tablets or servers.

[0009] Thus referring to Figure 1 , an instruction memory 12 provides instructions to an instructions fetch unit 14 in a pipeline 10. Those instructions are then decoded at the decode unit 16. Operand fetch 1 8 fetches operands from a data memory 24 for execution at execute unit 20. And the data is written back to the data memory 24 at write-back 22.

[0010] In order to achieve full backwards compatibility, unsupported instructions may be handled in different ways. According to one embodiment, shown in Figure 2, a full decoder 16 may be provided in the pipeline 1 0. This decoder, at the time of full instruction decoding, detects unimplemented instructions and invokes prebuilt handlers 34 in execution unit 20 for those instructions. These pre-built handlers are dedicated designs that handle a particular instruction or instruction type. These prebuilt handlers can be software or hardware based.

[001 1 ] This approach may use a full-blown or complete decoder that speeds up detection of unsupported instructions and execution of execution handles. These pre-built handlers can be software or hardware based.

[0012] This full blown decoder speeds up detection of unsupported instructions and execution of execution handlers. The decoder may be divided into two parts. One part decodes commonly executed instructions and the second part decodes less frequently used instructions.

[0013] Thus referring to Figure 2, the instructions are received by decode unit 16. In this embodiment, the decode unit 16 may include an instruction parser 26 that detects which instructions are supported by the partial core 32 (which may be described as commonly executed instructions) and which instructions are not supported (which may be called less commonly or uncommonly executed instructions). The instructions that are supported by the partial core are decoded by a commonly executed decoder 28 and passed to the partial core 32. Instructions that are uncommonly executed or unsupported are decoded by the decoder 30 and handled by pre-built handlers 34 in the execute unit 20 in one embodiment.

[0014] In some embodiments, a sequence 36 shown in Figure 3, may be implemented in software, firmware and/or hardware. In software and firmware embodiments the sequence may be implemented by computer readable instructions stored in a non-transitory computer readable medium such as an optical,

semiconductor or magnetic storage.

[0015] The sequence 36, shown in Figure 3 begins by parsing the instructions as indicated in block 38. Namely the instructions may be parsed based on identifying instructions that are supported by the partial core and instructions that are not supported by the partial core. In one embodiment the supported instructions are the commonly executed instructions. In other embodiments, particular instructions may be parsed out because they are ones that are supported by the partial core.

[0016] As indicated in block 40 the instructions of one type are sent to the first decoder and instructions of the second type are sent to the second decoder 30. Then the decoded instructions of the first type are sent to the partial core and the decoded instructions of the second type are sent to the prebuilt handlers 34 as shown in block 42.

[0017] According to another embodiment, a core may generate an undefined instruction exception. This may be an existing exception or a newly defined special exception. The exception may be generated when an instruction is encountered that is unsupported by the partial core. Then a software or binary translation layer may get control of execution or resolve the exception. For example, in one embodiment the binary translation layer may execute a handler program that emulates the unsupported instruction.

[0018] In some embodiments, a hybrid of this approach and the previously described approach, shown in Figures 2 and 3 may be used. Thus referring to Figure 4, a sequence 44 may be implemented in software, firmware and/or hardware. In software and firmware embodiments the sequence may be

implemented by computer readable instructions stored on a non-transitory computer readable medium such as a magnetic, optical or semiconductor storage.

[0019] The sequence 44 begins by determining whether the instruction is supported as indicated in diamond 46. If so, the instruction may be executed in the partial core as indicated in block 48. Otherwise an exception is issued as indicated in block 50.

[0020] In accordance with yet another embodiment, a processor may have one or two cores that include the full and complete instruction set and some number of partial cores that only implement a certain feature of the completed instruction set such as commonly executed features. Whenever a partial core comes across an unsupported instruction, the partial core transfers that task to one of the complete cores. The complete core in the mixed or heterogeneous environment can be hidden or exposed to operating systems. This approach does not involve any binary translation layer, either software or hardware in some embodiments, and differences in core features can be hidden from the operating system in other software layers.

[0021 ] Thus, referring to Figure 5, the architecture may include at least one complete core 50 and at least one partial core 52. Instructions are checked by the partial core 52. Instructions are checked by the partial core 52. If the instructions are unsupported then they are transferred to the complete core 50. Other cases where instructions are transferred, may also be contemplated.

[0022] In accordance with one embodiment of a partial core processor, the following instructions may be supported:

Data Transfer

bswap, xchg, xadd, cmpxchg,

mov, push, pop, movsx, movzx,

cbw, cwd, cmovcc Arithmetic

add, ade, sub, sbb, imul, mul, idiv , div, inc, dec. neg, cmp

Logical and, or, xor, not

Shift and Rotate sar, shr, sal, shl, ror, rol, rer, rcl

Bit and Byte bt, bts, btr, btc, test

Control Transfer jmp, jcc, call, ret, iret, int, into

Flag Control stc, clc, cmc, pushf, popf, sti, cli

Miscellaneous lea, nop, ud2

System lidt , lock, sidt, hit, rdmsr, wrmsr

[0023] The following instructions may not be supported in accordance with one embodiment:

Data Transfer

cmpxchg8b, pusha, popa

Decimal Arithmetric

daa, das, aaa, aas, aam, aad

Shift and Rotate

shrd, shld

Bit and Byte

setee, bound, bsf, bsr

Control Transfer

enter, leave

String

movsb, movsw, movsd, cmpsb,

cmpsb, cmpsw, cmpsd, scash,

scasw, scads, loadsb, loadsw,

loaded, stosb, stows, stosd,

String

rep, repz, repnz

I/O

in, out, insb, insw, insd,

outsb, outsw, outsb

Flag Control

eld, std, lahf, sahf

Segment Register

Ids, les, lfs, lgs, lss

Miscellaneous

xlat , cupid, movebe System

lgdt, sgdt, lldt, sldt, ltr,

str, lmsw, smsw, cits, arpl,

lar, lsl, verr, verw, invd,

wbinvd, invlpg, rsun, rdpmc,

rdtsep, sysenter, sysexit,

xsave, xrestr, xgetbv, xsetbv

[0024] References throughout this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one implementation encompassed within the present invention. Thus, appearances of the phrase "one embodiment" or "in an embodiment" are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be instituted in other suitable forms other than the particular embodiment illustrated and all such forms may be encompassed within the claims of the present application.

[0025] While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous

modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention.